docs: cut 1.0.37 changelog#457
Merged
Merged
Conversation
wxianfeng
approved these changes
Jun 11, 2026
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
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.
Cut the 1.0.37 changelog. Two items in this release:
1.0.36stayed on the original unguarded cut (the release workflow's npm publish step failed with403 cannot publish over the previously published versions). 1.0.37 is the first version where every channel — GitHub releases,dws upgrade, install scripts, npm — ships the same guarded build.--yes.After merge: tag
v1.0.37on main → goreleaser publishes GitHub + npm. The npm publish step should succeed this time since 1.0.37 has never been published.