-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Build: Replace "release" with "build" in script for building a package #23063
Conversation
Size Change: 0 B Total Size: 1.13 MB ℹ️ View Unchanged
|
Ideally, it would just do the release :) what's preventing us from doing everything in the command like the plugin release? |
That should probably be a separate script/command which leverages build-plugin-zip.sh for building the ZIP. |
e570235
to
1a71c53
Compare
@youknowriad, I think that sometimes you might still want to test the zip file locally. |
The release command could stop and ask for confirmation like we do for plugins. |
Makes it easier to replace the underlying script without updating the docs
ooohh, I just read this properly, don't mind my comments. I was thinking about the "npm release command" while this is clearly about the plugin zip script. I'm not awake properly this morning :P |
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.
I can see how this would be frightening 😅
See: WordPress/gutenberg#23063 Changed from `package-plugin` to `build:plugin-zip`
Description
It was quite confusing to read "Time to release Gutenberg" after running the
npm run package-plugin
command. I immediately cancelled the task and had to check the source first if it's really doing a release. Well, it doesn't… 😓