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.

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

Release Automation Break #496

Open
AlfredoG87 opened this issue Jan 14, 2025 · 0 comments · May be fixed by #498
Open

Release Automation Break #496

AlfredoG87 opened this issue Jan 14, 2025 · 0 comments · May be fixed by #498
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs

Comments

@AlfredoG87
Copy link
Contributor

AlfredoG87 commented Jan 14, 2025

Description

The current Release automation WF got broken after the update of a dependabot upgrade version for the GHA that relies on to create a pull request for the next snapshot version.

peter-evans/create-pull-request from 6.1.0 to 7.0.6 (#477

see the parameters that the GHA takes on https://github.com/hashgraph/hedera-block-node/blob/main/.github/workflows/release-automation.yaml#L200-L208

Steps to reproduce

Only happens on the first run of a new Release.

follow steps on Release: #494
Cannot verify that the PR for snapshot was created, however, since the branch release/0.3 was already created, even if we run again the WF it wont attempt to create a new PR for bump version to 0.4.0-SNAPSHOT

Additional context

https://github.com/peter-evans/create-pull-request/tree/v7.0.6

The Action did not fail, just did not do what it should have done, wich is to create the PR.
https://github.com/hashgraph/hedera-block-node/actions/runs/12776059648/job/35613930315
already downloaded the WF logs in case the above link fails:
logs_33059885889.zip

Hedera network

No response

Version

v0.3.0-rc1

Operating system

None

@AlfredoG87 AlfredoG87 added the Bug A error that causes the feature to behave differently than what was expected based on design docs label Jan 14, 2025
@AlfredoG87 AlfredoG87 linked a pull request Jan 15, 2025 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant