Skip to content

Add a doc note for releasing a new provider version #452

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

Merged
legal90 merged 1 commit into from
May 25, 2023
Merged

Add a doc note for releasing a new provider version #452

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,3 +78,31 @@ Run acceptance tests:
$ bundle exec rake acceptance:run
...
```

### Releasing a New Provider Version

_Note: Only the owners of `vagrant-parallels` gem on https://rubygems.org are permitted
to release new versions._

1. Build and test the new gem version (see details above):
```
$ bundle exec rake build
```

2. Update the gem version in `./lib/vagrant-parallels/version.rb`

3. Update change log in `./CHANGELOG.md`

4. Commit those changes and also tag the release with the version:
```sh
$ git tag vX.Y.Z
$ git push --tags
```

4. Push a new gem version to rubygems.org:
```sh
$ gem push ./pkg/vagrant-parallels-<version>.gem
```

5. Create a new Release on Github from the newly pushed tag: https://github.com/Parallels/vagrant-parallels/tags.
More info on the doc page: [Managing releases in a repository](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository)