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.

Sign up for GitHub

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

Jump to bottom

chore: remove release-as for w3up-client in release-please-config.json #664

Merged
merged 2 commits into from
Mar 28, 2023
Merged

chore: remove release-as for w3up-client in release-please-config.json #664

merged 2 commits into from
Mar 28, 2023

Conversation

gobengo
Copy link
Contributor

@gobengo gobengo commented Mar 28, 2023 •
edited
Loading

Motivation:

@gobengo
Update release-please-config.json
460bc19 
Motivation:
* we don't need this now that 5.2.0 was released
@gobengo gobengo self-assigned this Mar 28, 2023
@gobengo gobengo requested a review from travis March 28, 2023 18:33
@gobengo gobengo changed the title Update release-please-config.json chore: remove release-as for w3up-client in release-please-config.json Mar 28, 2023
@gobengo gobengo marked this pull request as ready for review March 28, 2023 18:34
@gobengo gobengo added this to the w3up phase 4 milestone Mar 28, 2023
@gobengo gobengo merged commit 4818fb6 into main Mar 28, 2023
@gobengo gobengo deleted the gobengo-patch-1 branch March 28, 2023 18:47
gobengo added a commit that referenced this pull request Apr 11, 2023
@gobengo
chore: remove release-as for w3up-client in release-please-config.json (
e5ce93d 
#664)

Motivation:
* we don't need this now that 5.2.0 was released
* planned followup to
#662 (which was required
to get release-please-action to detect the right next release number in
a new repo)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@travis travis travis approved these changes

Assignees

@gobengo gobengo

Labels
None yet
Projects
None yet
Milestone
w3up phase 4
Development

Successfully merging this pull request may close these issues.
2 participants
@gobengo @travis