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

Updating release procedure #480

Merged
merged 1 commit into from
Dec 19, 2024
Merged

Updating release procedure #480

Show file tree
Hide file tree
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
7 changes: 7 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,13 @@
CHANGELOG
=========

## 0.27.4

### Improvements

- Added secret support for all fields in DeploymentSettings [#467](https://github.com/pulumi/pulumi-pulumiservice/pull/467)
- Added cascading secrets to Deployment settings [#475](https://github.com/pulumi/pulumi-pulumiservice/pull/475)

## 0.27.3

### Bug Fixes
Expand Down
7 changes: 0 additions & 7 deletions CHANGELOG_PENDING.md
View file
Open in desktop

This file was deleted.

32 changes: 13 additions & 19 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ You should also test changes manually using a Pulumi program that uses the updat

For contributors we use the [standard fork based workflow](https://gist.github.com/Chaser324/ce0505fbed06b947d962): Fork this repository, create a topic branch, and when ready, open a pull request from your fork.

We require a changelog entry for pretty much all PRs. Add a line in `CHANGELOG_PENDING.md` describing your change and link to an issue. See `CHANGELOG.md` for examples. In rare cases where your PR is a minor change, like formatting or a typo fix, apply `impact/no-changelog-required` label to your PR instead.
We require a changelog entry for pretty much all PRs. Add a line in `CHANGELOG.md` describing your change and link to an issue. In rare cases where your PR is a minor change, like formatting or a typo fix, apply `impact/no-changelog-required` label to your PR instead.

### Pulumi employees

Expand All @@ -56,24 +56,18 @@ Please ensure that you nest your branches under a unique identifier such as your

This section is for Pulumi employees only.

To release a new version of the provider, follow the procedure below:
1. Create a release
- Run below commands, replacing `X.XX.XX` with your new version. This will use your codefreeze commit as source for the new release.
```
git checkout main
git pull
git tag sdk/vX.XX.XX
git tag vX.XX.XX
git push origin vX.XX.XX
git push origin sdk/vX.XX.XX
```
- Github Actions will automatically build, test and then publish the new release to all the various package managers
- Once that is done, you will see your version in [Releases](https://github.com/pulumi/pulumi-pulumiservice/releases)
- The version will have a description from `CHANGELOG_PENDING.md`
1. Codefreeze
- Move all the items from `CHANGELOG_PENDING.md` to `CHANGELOG.md`, under a new version that you are releasing
- Make a PR like [this example](https://github.com/pulumi/pulumi-pulumiservice/pull/255)
- Get an approval and merge it in
To release a new version of the provider, follow steps below:
- Run release commands, replacing `X.XX.XX` with your new version.
```
git checkout main
git pull
git tag sdk/vX.XX.XX
git tag vX.XX.XX
git push origin vX.XX.XX
git push origin sdk/vX.XX.XX
```
- Github Actions will automatically build, test and then publish the new release to all the various package managers
- Once that is done, you will see your version in [Releases](https://github.com/pulumi/pulumi-pulumiservice/releases)

## Getting Help

Expand Down
Loading