-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
added provisioning state to grants (#15)
* added provisioning state to grants * added grant change type * remove grant provisioning change state * add changeset --------- Co-authored-by: Josh Wilkes <[email protected]>
- Loading branch information
1 parent
260c28d
commit d22a3fe
Showing
6 changed files
with
47 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
--- | ||
"@common-fate/sdk": minor | ||
--- | ||
|
||
add "provisioning" grant status |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# Releasing and change management | ||
|
||
## Minor version | ||
|
||
1. Create a new minor version changeset and merge it to main `pnpm changeset` | ||
2. Merge the automated changesets PR `Version Packages for main` this will tag and release a new version | ||
|
||
## Patch version | ||
|
||
1. Create a patch changeset and merge it to main `pnpm changeset` | ||
2. If you are ready to release this change, Merge the automated changesets PR `Version Packages for main` this will tag and release a new version | ||
|
||
## Backporting changes to older minor versions | ||
|
||
1. Check for an existing release branch e.g `release/v1.*` for the minor version you are back porting to | ||
2. If the branch doesn't exist, checkout the commit associated with the minor release you want to backport to | ||
3. Run `./create-minor-release.sh` and when prompted set the release branch version e.g `v1.1` or `v1.2` excluding the patch version | ||
4. Push the branch | ||
5. You can now push your changes to this release branch, you may choose to cherrypick the patch from main | ||
6. Create a patch changeset and merge it to the release branch `pnpm changeset` | ||
7. If you are ready to release this change, Merge the automated changesets PR matching your release branch `Version Packages for release/v1.*` this will tag and release a new version |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters