Repository navigation
Retry starter lockfile install when core is unpublished - #62
Merged
Merged
Conversation
Version Packages merges bump @dashcommerce/core in git before the local OTP publish reaches npm. Sync then fails permanently on `bun install`. Retry that missing-version race for a few minutes and fail immediately on any other install error. Co-authored-by: Timchosen Uzua <timchosen@gmail.com>
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.
Sync failed on main after Version Packages merge #61: the "Regenerate standalone lockfile" step ran
bun installwith@dashcommerce/corepinned to^0.3.3before that version was on npm (publish is local OTP, after the merge).Failed run: https://github.com/emdashCommerce/dashcommerce/actions/runs/41427275420
This retries
bun installonly for that unpublished-core error, for about five minutes with backoff (15s, 30s, 45s, then 60s). Other install failures still fail the job on the first attempt. Retries pass--forceso bun does not reuse a 5-minute-stale registry manifest from the first miss. After eight attempts the step errors with a note to publish, then re-run the workflow.Please merge with a merge commit, not a squash.
CI on this PR is typecheck/build/test. Sync itself only runs on push to main (or workflow_dispatch). Merging this re-runs Sync, which should catch the starter up now that 0.3.3 is on npm.