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

build: Publish to JSR and update release-please config #10

Merged
merged 3 commits into from
Jul 12, 2024

Conversation

nzakas
Copy link
Member

@nzakas nzakas commented Jul 9, 2024

Prerequisites checklist

What is the purpose of this pull request?

Tweak the release-please behavior

What changes did you make? (Give an overview)

  • Publish package to JSR
  • Simplified release-please-config.json because this isn't a monorepo

Related Issues

Is there anything you'd like reviewers to focus on?

@@ -1,18 +1,13 @@
{
"bootstrap-sha": "505795a1312e90f1ce3b59b530622929bc38b4fe",
"last-release-sha": "48545ebe503d661af0562b240648253199758d9f",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this necessary? I believe we'd need to remove it after the next successful release, so if it isn't necessary it might be better not to add it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's required when there's a change in the tag format, but since we're not doing that, this is unnecessary.

"bump-minor-pre-major": true,
"packages": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you sure we can avoid having packages in the config? Per the docs, "the minimal content required defines at least one package".

https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md#configfile

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, good question. I thought it wasn't necessary because all of the same properties are on the root level, but looking at the JSON Schema, it is indeed necessary. I'll revert this.

Copy link
Member

@mdjermanovic mdjermanovic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@mdjermanovic mdjermanovic merged commit 576e899 into main Jul 12, 2024
12 checks passed
@mdjermanovic mdjermanovic deleted the release-please-update branch July 12, 2024 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants