feat: add changeset validation and release workflow#5673
Merged
Conversation
| - name: Use Node.js | ||
| uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0 | ||
| with: | ||
| node-version: lts/* |
Member
There was a problem hiding this comment.
lts is too dynamic for our releases because we try to target the lowest possible node version supported.
Member
Author
There was a problem hiding this comment.
Member
There was a problem hiding this comment.
It is normal to use it for releases, we will have the latest version
alexander-akait
approved these changes
May 18, 2026
Member
alexander-akait
left a comment
alexander-akait
left a comment
There was a problem hiding this comment.
Looks good, let's fix tests before merge
bjohansebas
force-pushed
the
github-actions-release
branch
from
5c24dfe to
8a99d55
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## next #5673 +/- ##
=======================================
Coverage 88.84% 88.84%
=======================================
Files 13 13
Lines 5838 5838
=======================================
Hits 5187 5187
Misses 651 651 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
bjohansebas
added a commit
that referenced
this pull request
May 23, 2026
* feat: add changeset validation and release workflow * chore: add changes * chore: fix package-lock * chore: update http-proxy-middleware to v4 * docs: update migration guide with ESM-only and Express v5 changes * chore: update webpack-dev-middleware to v8 and document breaking changes * chore: update imports to use node: prefix and replace regex with replaceAll * chore: update qs to v6.15.2 and ws to v8.21.0 in package-lock.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
What kind of change does this PR introduce?
Did you add tests for your changes?
Does this PR introduce a breaking change?
If relevant, what needs to be documented once your changes are merged or what have you already documented?
Use of AI