Skip to content

docs(facade): describe 0.6.51 and release it as 0.6.51 - #250

Draft
AndrewKirkovski wants to merge 1 commit into
masterfrom
chore/facade-release-as-0.6.51
Draft

AndrewKirkovski wants to merge 1 commit into
masterfrom
chore/facade-release-as-0.6.51

Conversation

@AndrewKirkovski

Copy link
Copy Markdown
Contributor

Makes the next facade release 0.6.51 instead of 0.6.50.

Facade 0.6.50 is already on the Hub. It was published by hand from #245, and the tag facade-v0.6.50 and its GitHub release exist. The release manifest still records 0.6.49, so the release PR #249 proposes facade: 0.6.50 for #248. Merging #249 as it is would try to tag and publish 0.6.50 a second time.

This PR touches only src/facade, so its override applies to the facade only. Views stays at 0.5.14. It uses Release Please's supported override, as #217 did for 0.6.48 after the hand-published 0.6.47. The README status line now describes 0.6.51.

After this merges, #249 should propose facade: 0.6.51 and views: 0.5.14.

Release-As: 0.6.51

Facade 0.6.50 was published to the Hub by hand from #245, while the
release manifest still records 0.6.49, so Release Please would propose
0.6.50 again. This uses Release Please's supported override to release
the next unused patch, as #217 did for 0.6.48. The README status line now
describes 0.6.51, which adds wippy.facade:host_url for Views fragment
pages.

Release-As: 0.6.51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant