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

Update signing procedure #1075

Merged
merged 2 commits into from
Jan 12, 2025
Merged

Conversation

ann0see
Copy link
Member

@ann0see ann0see commented Dec 23, 2024

Short description of changes
Updates the signing procedure to the new repo. Also fixes some broken markdown.

Context: Fixes an issue? Related issues
Fixes: #1046

Status of this Pull Request

Ready for review

What is missing until this pull request can be merged?

Review

Does this need translation?

No.

Checklist

  • I've verified that this Pull Request follows the general code principles
  • I waited some time after this Pull Request was opened and all GitHub checks completed without errors.
  • I'm sure that this Pull Request goes to the correct branch

@ann0see ann0see added this to the Release 3.12.0 milestone Dec 23, 2024
@ann0see ann0see requested a review from pljones December 23, 2024 20:07
@ann0see ann0see marked this pull request as draft December 23, 2024 20:25
@ann0see
Copy link
Member Author

ann0see commented Dec 23, 2024

Seems as if there's a syntax error in pt-BR?

@pljones
Copy link
Contributor

pljones commented Dec 23, 2024

Approved but I've a question -- is just pushing the tag enough? If your repo isn't already up to date, the tag will point to a non-existent (as yet) commit, so the build will fail. The "inform..." bit was to all emlynmac to pull from upstream and then pull the tags and push for his build.

@ann0see
Copy link
Member Author

ann0see commented Dec 23, 2024

Not sure. I thought pushing a tag was enough: I did so in the past with a non existent commit on upstream.

@pljones
Copy link
Contributor

pljones commented Dec 23, 2024

Interesting. Maybe github is clever enough to follow the upstream chain in the build.

@ann0see ann0see linked an issue Dec 23, 2024 that may be closed by this pull request
Copy link
Member Author

@ann0see ann0see left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume there's another broken bracket somewhere breaking the build.

contribute/en/Release-Process.md Outdated Show resolved Hide resolved
@ann0see ann0see marked this pull request as ready for review January 11, 2025 10:28
@ann0see
Copy link
Member Author

ann0see commented Jan 11, 2025

Ok. Doesn't seem like it

@ann0see
Copy link
Member Author

ann0see commented Jan 11, 2025

@pljones
I think it's done now. Just waiting for the CI to finish

@ann0see ann0see merged commit d6e7ef5 into jamulussoftware:next-release Jan 12, 2025
1 check passed
@ann0see ann0see deleted the fixSigningMac branch January 12, 2025 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Clean up macOS signing procedure
2 participants