You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have faced a significant disruption due to a small typo in Merge Gatekeeper code base, which caused all of our internal CI setup to fail and block us from merging PRs. This was related to the release, but also how we used main as the version reference.
If this has caused any disruption to your workflow, we are extremely sorry for not catching this earlier, and will aim to provide better control for future changes.
As preventative measures, we will be updating some of the documentation to note how you should be using v1 tag (or more specific version such as v1.1, v1.0.2, etc.). Those will be updated after we do extra testing internally and ensure the stability of the latest code base. Also, we will work to add more strict test cases and close reviews to catch any unwanted behaviours.
This discussion was created from the release v1.1.1.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Patch Release
v1.1.0 includes the bug fix for handling GitHub Actions with "failure" state.
Details of This Release
🎁 Features
None
🐞 Bug Fixes
failure
state handling Addfailure
state handling #38 (fixes Gatekeeper does not fail if the webhook job fails #36)🔬 Misc
None
Other Note
(Copied from the previous release)
We have faced a significant disruption due to a small typo in Merge Gatekeeper code base, which caused all of our internal CI setup to fail and block us from merging PRs. This was related to the release, but also how we used
main
as the version reference.If this has caused any disruption to your workflow, we are extremely sorry for not catching this earlier, and will aim to provide better control for future changes.
As preventative measures, we will be updating some of the documentation to note how you should be using
v1
tag (or more specific version such asv1.1
,v1.0.2
, etc.). Those will be updated after we do extra testing internally and ensure the stability of the latest code base. Also, we will work to add more strict test cases and close reviews to catch any unwanted behaviours.This discussion was created from the release v1.1.1.
Beta Was this translation helpful? Give feedback.
All reactions