-
Notifications
You must be signed in to change notification settings - Fork 6.8k
build: set up all packages to publish via wombot proxy #17679
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
Conversation
91a0b8e
to
f9069b2
Compare
f9069b2
to
4307b7e
Compare
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.
LGTM. For reference: We remove the NPM auth stuff since we'll switch to releasing from CI anyway in the future. We should make it clear in the release instructions somehow though?
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.
LGTM
tools/release/publish-release.ts
Outdated
@@ -130,6 +130,9 @@ class PublishReleaseTask extends BaseReleaseTask { | |||
console.info(chalk.green(chalk.bold(` ✓ Published all packages successfully`))); | |||
console.info(chalk.yellow(` ⚠ Please draft a new release of the version on Github.`)); | |||
console.info(chalk.yellow(` ${newReleaseUrl}`)); | |||
|
|||
// Remove file at ~/.npmrc after release is complete. | |||
spawnSync('rm', ['~/.npmrc'], {cwd: this.projectDir, stdio: 'inherit', shell: true}); |
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.
Why not use NodeJS unlinkSync? Not a big deal though, so I'm happy leaving it like that.
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.
Done, didn't even know it existed.
ee90a21
to
35a5167
Compare
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
No description provided.