- handbook
- Company
- Company
- Board
- Communications
- Decision making
- Guides
- KPIs and OKRs
- principles
- Remote Work
- Security
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Third-Party Risk Management Policy
- Human Resources Security Policy
- Access Control Policy
- Incident Response Plan
- Cryptography Policy
- Information Security Policy and Acceptable Use Policy
- Secure Development Policy
- Data Management Policy
- strategy
- values
- Operations
- Product
- Feedback
- Market Segments
- Metrics
- Node-RED Dashboard
- personas
- Pricing Principles
- Principles
- Responsibilities
- Strategy
- Versioning
- Customer department
- Customer
- Customer Success
- Hubspot
- Marketing
- How we work
- Marketing
- Video
- Customer Stories
- Social Media
- blog
- Community
- Marketing - Website
- Webinars
- FlowFuse Messaging
- Sales
- Engineering & Design Practices
- Design
- Engineering
- Certified Nodes
- contributing
- Front End
- Packaging Guidelines
- Platform Ops
- Deployment
- Incident Response
- Observability
- Production Environment
- FlowFuse Dedicated
- Staging Environment
- Project Management
- Releases
- Security Policy
- tools
- Website A/B Testing
- Internal Operations
- People Ops
# Dashboard 2.0 Release Process
The following steps are taken in order to cut a release for Node-RED Dashboard 2.0:
# Code (Version) Updates
- Update the
package.jsonto the new version number npm installlocally to update thepackage-lock.json- Commit the changes to the two files to a new branch named
vX.Y.X - Push the changes to the branch, and open a Pull Request, titled
vX.Y.X - Have someone else review the Pull Request, and merge when approved
# GitHub Release
- Navigate to the Dashboard Releases page and click "Draft a new release"
- In the "Choose a tag" dropdown, type in the new version number, and select the "Create new tag vX.Y.X" option
- Select "Generate release notes", this will auto-populate with all Pull Requests contained within the release.
- Manually group the list of PRs in the release notes into the following categories:
- New Widgets & Variations: For any new widgets/nodes, or types of a widget, e.g. new chart types or gauge types.
- Fixes & Improvements: Bug fixes and/or smaller improvements to existing code.
- Documentation: Any PRs dedicated to documentation improvements.
- Dependencies: PRs linked to changing a version number of a dependency, or adding a new dependency.
- Administration: PRs that are related to the administration of the repository, e.g. CI/CD changes, etc.
- Click "Publish Release"
- Doing so will automatically trigger the publication of the updates to npm via a GitHub Action
# Publish to Node-RED Palette Manager
Once the package has been updated on npm, you need to update the entry for Dashboard 2.0 in Node-RED Palette Manager too:
- Navigate to the "Adding a node" section of the Node-RED Palette Manager
- Enter
@flowfuse/node-red-dashboardinto the library name field - Click "Add Node"
Within the next 25-30 minutes, the entry Node-RED's Palette Manager will live update for all Node-RED's worldwide.