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.

Sign up for GitHub

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

Jump to bottom

Test, Fix and Follow-up on "Automated release process" attempt to release 0.1.0-rc1 and 0.1.0-rc2 versions. #229

Closed
2 tasks done
Tracked by #39
AlfredoG87 opened this issue Oct 2, 2024 · 2 comments · Fixed by #236
Closed
2 tasks done
Tracked by #39

Test, Fix and Follow-up on "Automated release process" attempt to release 0.1.0-rc1 and 0.1.0-rc2 versions. #229

AlfredoG87 opened this issue Oct 2, 2024 · 2 comments · Fixed by #236
Assignees
@AlfredoG87
Labels
P2 Required to be completed in the assigned milestone, but may or may not impact release schedule.
Milestone
0.1.0

Comments

@AlfredoG87
Copy link
Contributor

AlfredoG87 commented Oct 2, 2024 •
edited by rbarkerSL
Loading

Recently the release-automation.yaml was merged into main to start automate the release process, however as expected, after merging, is necessary to do some adjustments, fixes and configurations to the repo to be able to iron-out the WF. This is expected since this is a fairly complex workflow with variables that are hard (close to impossible) to replicate locally.

This tasks is a place-holder for the testing phase.

So far this has come up:

  • Change secrets.HEDERA_BOT_TOKEN for secrets.GITHUB_TOKEN at the checkout step.
  • Requested RE team to add the following secrets to the repo: secrets.GPG_PRIVATE_KEY and secrets.GPG_PASSPHRASE

The conclusion of this ticket is to iron-out the process and verify is working by sucessfully releasing 0.1.0 starting with attempt to release 0.1.0-rc1 and 0.1.0-rc2 versions.
@AlfredoG87 AlfredoG87 mentioned this issue Oct 2, 2024
Closed
@AlfredoG87 AlfredoG87 self-assigned this Oct 2, 2024
@AlfredoG87 AlfredoG87 added the P2 Required to be completed in the assigned milestone, but may or may not impact release schedule. label Oct 2, 2024
@AlfredoG87 AlfredoG87 added this to the 0.1.0 milestone Oct 2, 2024
@AlfredoG87 AlfredoG87 mentioned this issue Oct 2, 2024
Closed
2 tasks
@AlfredoG87 AlfredoG87 changed the title Test, Fix and Follow-up on Release process, attempt to release 0.1.0-rc1 and 0.1.0-rc2 versions. Test, Fix and Follow-up on "Automated release process" attempt to release 0.1.0-rc1 and 0.1.0-rc2 versions. Oct 2, 2024
@AlfredoG87
Copy link
Contributor Author

@rbarkerSL
https://swirldslabs-help.freshdesk.com/support/tickets/5749

@rbarkerSL rbarkerSL mentioned this issue Oct 9, 2024
Merged
@rbarkerSL
Copy link
Contributor

PR #236 will complete this ticket. @AlfredoG87

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlfredoG87 AlfredoG87

Labels
P2 Required to be completed in the assigned milestone, but may or may not impact release schedule.
Projects
None yet
Milestone
0.1.0
2 participants
@AlfredoG87 @rbarkerSL