Skip to content
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

Making a release with new options / 1.19.0 “post mortem” #6887

Closed
lydell opened this issue Nov 9, 2019 · 4 comments
Closed

Making a release with new options / 1.19.0 “post mortem” #6887

lydell opened this issue Nov 9, 2019 · 4 comments
Assignees
Labels
locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting. type:infra Issues about CI, publishing to npm, or similar type:meta Issues about the status of Prettier, or anything else about Prettier itself

Comments

@lydell
Copy link
Member

lydell commented Nov 9, 2019

All options in Prettier have a since: "x.y.z" field.

The new option in 1.19, vueIndentScriptAndStyle, had since: "1.19.0".

prettier --support-info apparently does not print stuff with a higher since version than is specified in package.json.

The release script bumps the version in package.json and then runs the tests. The tests for prettier --support-info then fail, because now it returns the new option added in 1.19.0 which isn’t in the snapshots.

I worked around this issue by first making a commit where I bumped the version in package.json to 1.19.0-beta.1 and updated the snapshots:

057e15d

However, we now have this in our code:

vueIndentScriptAndStyle: {
    since: "1.19.0-beta.1",

The questions of this issue are:

  • Is since: "1.19.0-beta.1" a problem? EDIT: Changed to since: "1.19.0" in 1.19.1.
  • Does the release script need updating to handle new options?
  • Should the PR adding the new vueIndentScriptAndStyle have done something differently?

@duailibe do you have any insight?

@lipis lipis mentioned this issue Nov 9, 2019
12 tasks
lydell added a commit that referenced this issue Nov 9, 2019
lydell added a commit that referenced this issue Nov 9, 2019
@thorn0 thorn0 added type:infra Issues about CI, publishing to npm, or similar type:meta Issues about the status of Prettier, or anything else about Prettier itself labels Nov 11, 2019
@duailibe
Copy link
Member

@lydell If I understand correctly, what's missing in the release script is to change package.json version back to "NEXTVERSION-dev". Does that make sense?

@lydell
Copy link
Member Author

lydell commented Nov 13, 2019

Another way would be to default version in getSupportInfo(version, opts) to "999.9.9" rather than require("../../package.json").version.split("-", 1)[0] I guess. Or something like that – not passing a version should mean “give me everything”. One should ideally not have to update the snapshots when bumping the version.

@fisker
Copy link
Member

fisker commented Apr 18, 2020

Is this still a problem? There will be a new option in v2.1

@thorn0 thorn0 self-assigned this Apr 18, 2020
@thorn0
Copy link
Member

thorn0 commented Apr 19, 2020

No longer a problem. The version in package.json is already set to 2.1.0-dev, so the snapshots don't change after changing it to 2.1.0. The problem with 1.19.0 was that the version in package.json wasn't set to 1.19.0-dev after releasing 1.18.2. No idea why. The release script should have done that.

@thorn0 thorn0 closed this as completed Apr 19, 2020
@github-actions github-actions bot added the locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting. label Jul 19, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting. type:infra Issues about CI, publishing to npm, or similar type:meta Issues about the status of Prettier, or anything else about Prettier itself
Projects
None yet
Development

No branches or pull requests

4 participants