Skip to content

Commit

Permalink
fix(ci): update from published to released trigger for deployment epic (
Browse files Browse the repository at this point in the history
celestiaorg#3351)

<!--
Thank you for submitting a pull request!

Please make sure you have reviewed our contributors guide before
submitting your
first PR.

Please ensure you've addressed or included references to any related
issues.

Tips:
- Use keywords like "closes" or "fixes" followed by an issue number to
automatically close related issues when the PR is merged (e.g., "closes
celestiaorg#123" or "fixes celestiaorg#123").
- Describe the changes made in the PR.
- Ensure the PR has one of the required tags (kind:fix, kind:misc,
kind:break!, kind:refactor, kind:feat, kind:deps, kind:docs, kind:ci,
kind:chore, kind:testing)

-->
I realized that the `published` event is triggered by pre-releases too. 
The `released` event is only triggered when we set the release to the
latest release, which is what we want to track for deployments.
  • Loading branch information
MSevey committed May 1, 2024
1 parent b6a77a6 commit 40ee3c5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion .github/workflows/create_release_tracking_epic.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ name: Create Release Tracking Epic
# on slack for tracking the deployment of a release to testnets and mainnet.
on:
release:
types: [published]
types: [released]
jobs:
trigger_issue:
uses: celestiaorg/.github/.github/workflows/reusable_create_release_tracking_epic.yml@v0.4.1
Expand Down

0 comments on commit 40ee3c5

Please sign in to comment.