New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable publish retrying #1458
Open
NullVoxPopuli
wants to merge
6
commits into
main
Choose a base branch
from
enable-publish-retrying
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Enable publish retrying #1458
Conversation
This file contains 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
NullVoxPopuli
commented
Oct 24, 2023
@@ -2,27 +2,30 @@ | |||
"name": "@glimmer-workspace/bin", | |||
"private": true, | |||
"dependencies": { | |||
"puppeteer-chromium-resolver": "^20.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
running pnpm <anything>
sorts the package.json
NullVoxPopuli
commented
Oct 24, 2023
|
||
for (const pkg of packages('@glimmer')) { | ||
console.log(`${chalk.gray('# publishing')} ${chalk.cyanBright(pkg.name)}`); | ||
execSync('yalc publish --push', { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yalc wasn't even a dependency anywhere
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.
logic stolen from: https://github.com/embroider-build/embroider/blob/main/test-packages/unstable-release/publish.js
it's really only an issue if we do what we're doing right now where we try to publish the same tag over and over again due to config issues (or infra issues)
Changes
This removed
yalc-publish.mts
, which appears to be leftover from before the pnpm migration. yalc usednpm publish
, which doesn't supportworkspace:^
versions.in the
bin
package, swap esno for esyes, because we like positivity. Also, esyes doesn't compile to CJS like esno does.esyes
is in use by the starbeam family of projectsA New
pnpm-publish.mts
file is present, which implements iterate + try/catch for each package so that our workflow_dispatch way of deploying packages can work eventually.Testing
Testing locally with:
shows, since my npm user doesn't have access to publish (intentionally!):