Skip to content

Commit

Permalink
docs: remove angle brackets for bare URL
Browse files Browse the repository at this point in the history
  • Loading branch information
nix6839 committed Apr 18, 2023
1 parent 93014b6 commit eaf4551
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -230,15 +230,15 @@ git reset --hard

By default, every package with a changeset will be released. If you only want to target a smaller subset of packages for release, you can consider clearing out the `.changesets` directory to replace all existing changesets with a single changeset of only the packages that you want to release. Just be sure not to commit or push this to `main`, since it will destroy existing changesets that you will still want to eventually release.

Full documentation: <https://github.com/changesets/changesets/blob/main/docs/snapshot-releases.md>
Full documentation: https://github.com/changesets/changesets/blob/main/docs/snapshot-releases.md

### Releasing `astro@next` (aka "prerelease mode")

Sometimes, the repo will enter into "prerelease mode". In prerelease mode, our normal release process will publish npm versions under the `next` dist-tag, instead of the default `latest` tag. We do this from time-to-time to test large features before sharing them with the larger Astro audience.

While in prerelease mode, follow the normal release process to release `astro@next` instead of `astro@latest`. To release `astro@latest` instead, see [Releasing `astro@latest` while in prerelease mode](#releasing-astrolatest-while-in-prerelease-mode).

Full documentation: <https://github.com/changesets/changesets/blob/main/docs/prereleases.md>
Full documentation: https://github.com/changesets/changesets/blob/main/docs/prereleases.md

### Entering prerelease mode

Expand Down Expand Up @@ -271,7 +271,7 @@ When in prerelease mode, the automatic PR release process will no longer release
1. Run `pnpm exec release` to publish your new release.
1. Run `git push && git push --tags` to push your new release to GitHub.
1. Run `git push release/0.X:latest` to push your release branch to `latest`.
1. Go to <https://github.com/withastro/astro/releases/new> and create a new release. Copy the new changelog entry from <https://github.com/withastro/astro/blob/latest/packages/astro/CHANGELOG.md>.
1. Go to https://github.com/withastro/astro/releases/new and create a new release. Copy the new changelog entry from https://github.com/withastro/astro/blob/latest/packages/astro/CHANGELOG.md.
1. Post in Discord #announcements channel, if needed!

## Documentation
Expand Down

0 comments on commit eaf4551

Please sign in to comment.