Repository navigation
Keep staging current with master - #50
Merged
Merged
Conversation
The automatic release checked a second time, right before npm publish, that master still pointed at its source, and failed if another merge had landed during the build and checks. The workflow already runs the whole release in one concurrency group that never cancels a run in progress, so the newer merge waits and publishes next. Keep the check at the start, which still refuses a rerun of an older commit, and drop only the later comparison. Every other identity, registry and integrity check still runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Let a started npm release finish after newer merges (WORK-9253)
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.
Factory's staging catch-up: master has 2 commits staging does not, such as a hotfix or a release merge. This merges master 7c12c9e into staging, keeping everything staging already has.
It goes through staging's merge queue and required checks like any change. A conflict or failed check waits for a person; see https://factory.dealmachine.com/guides/guides-hotfixes.