Version v1.2.0#22
Merged
Merged
Conversation
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
1 participant
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
Release commit for v1.2.0. Bundles:
package.json/package-lock.jsonbumped from1.1.4to1.2.0.dist/index.jsregenerated vianpm run prepare.Why this exists as a PR
The org-level
quality-gateruleset requires changes tomainto go through a pull request. The release scriptupdate-version.shhistorically pushed straight tomain, which is no longer permitted. This PR carries the commit the script produced; tags will be created and pushed directly after merge (tags are not under the ruleset).Changes since v1.1.4
workflow_dispatchfor build description: fall back to fetching the commit message via the GitHub API when the event payload lackshead_commit.update-version.shwithset -euo pipefail.🤖 Generated with Claude Code