diff --git a/CHANGELOG.md b/CHANGELOG.md index 00936716b..b1eb42523 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -45,7 +45,7 @@ For the full list of changes, see the [0.11.0] release notes. - When a section's sidebar entries are truncated because there are more than [params.ui.sidebar_menu_truncate] section entries, a warning is issued. -[0.11.0]: https://github.com/google/docsy/releases/latest?FIXME=v0.X.Y +[0.11.0]: https://github.com/google/docsy/releases/v0.11.0 [bs-rtl]: https://getbootstrap.com/docs/5.3/getting-started/rtl/ [Adding a community page]: https://www.docsy.dev/docs/adding-content/content/#adding-a-community-page diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6deddb8c9..e922f2850 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -118,14 +118,14 @@ least one downstream project, then perform the following actions before any further changes are merged into the default branch: 1. Set `version` in [package.json](package.json) to the next planned (or the - next dot) release with a dev suffix, such as `v0.X.Z-dev.0-unreleased`. + next dot) release with a dev suffix, such as `v0.X.Z-dev-unreleased`. 2. In the [CHANGELOG]: - **Create a new entry** for the next release by copying the ENTRY TEMPLATE at the end of the file. - **Pin the 0.X.Y release URL**, which ends with `latest?FIXME=...`, to the v0.X.Y release at `https://github.com/google/docsy/releases/v0.x.y`. 3. **Submit a PR with your changes**, using a title like "Set NPM package - version to next unreleased dev vers". + version to next unreleased dev version". 4. **Get PR approved and merged**. [CHANGELOG]: CHANGELOG.md diff --git a/package.json b/package.json index 93ff8080c..925c7f168 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "docsy", - "version": "0.11.0", - "version.next": "0.11.1-dev.0-unreleased", + "version": "0.11.1-dev-unreleased", + "version.next": "0.12.0-dev-unreleased", "repository": "github:google/docsy", "homepage": "https://www.docsy.dev", "license": "Apache-2.0",