Skip to content

Commit fcff62e

Browse files
committed
fixup
Signed-off-by: Alexander Dahmen <alexander.dahmen@inovex.de>
1 parent 340b7cb commit fcff62e

File tree

2 files changed

+23
-1
lines changed

2 files changed

+23
-1
lines changed

.goreleaser.yaml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,6 @@ signs:
3333
- sign-blob
3434
- '-y'
3535
- '--verbose'
36-
- '--output-certificate=${certificate}'
3736
- "--output-signature=${signature}"
3837
- '--bundle=${signature}'
3938
- '${artifact}'

RELEASE.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# Release
2+
3+
## Release cycle
4+
5+
A release should be created at least every 2 weeks.
6+
7+
## Release creation
8+
9+
> [!IMPORTANT]
10+
> Consider informing / syncing with the team before creating a new release.
11+
12+
1. Check out latest main branch on your machine
13+
2. Create the following git tags:
14+
- `git tag provider/pkg/version/vX.X.X`
15+
- `git tag provider/shim/vX.X.X`
16+
- `git tag vX.X.X`
17+
3. Push the git tag: `git push origin --tags`
18+
4. The [release pipeline](https://github.com/stackitcloud/pulumi-stackit/actions/workflows/release.yaml) will build the release and publish it on GitHub
19+
5. Ensure the release was created properly using the
20+
- [GitHub releases page](https://github.com/stackitcloud/pulumi-stackit/releases)
21+
- [Pulumi registry](https://www.pulumi.com/registry/packages)
22+
6. Ensure the packages where properly published (e.g. to npm)
23+
- [npm](https://www.npmjs.com/)

0 commit comments

Comments
 (0)