Skip to content

3.22.0 publish changes#1555

Merged
saperi22 merged 5 commits into3.xfrom
3.x-publish
Apr 1, 2026
Merged

3.22.0 publish changes#1555
saperi22 merged 5 commits into3.xfrom
3.x-publish

Conversation

@saperi22
Copy link
Copy Markdown
Collaborator

@saperi22 saperi22 commented Mar 25, 2026 •
edited
Loading

Summary of changes

  • v3.22.0 was released manually since the publish scripts were very old.
  • merging in the changes that were used to publish 3.22.0 manually

Checklist

  • Added a changelog entry
  • Relevant test coverage
  • Tested and confirmed payment flows affected by this change are functioning as expected

Authors

List GitHub usernames for everyone who contributed to this pull request.

noguier
noguier reviewed Mar 25, 2026
View reviewed changes
Comment thread Rakefile
puts "PayPal modules have been released"
end

task :release_paypal_zscaler do
Copy link
Copy Markdown
Contributor

@noguier noguier Mar 25, 2026

Choose a reason for hiding this comment

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

do we still want to leave the zscaler command here? or should we just make them as release_braintree / release_paypal but with closeAndReleaseSonatypeStagingRepository in the same command?

Copy link
Copy Markdown
Collaborator Author

@saperi22 saperi22 Mar 26, 2026

Choose a reason for hiding this comment

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

🤷 I don't think I want to make too many changes on this one. We might not ever revisit it.

@saperi22 saperi22 marked this pull request as ready for review March 31, 2026 18:54
@saperi22 saperi22 requested a review from a team as a code owner March 31, 2026 18:54
@saralvasquez
Copy link
Copy Markdown
Contributor

saralvasquez commented Mar 31, 2026

I assume these are to make publishing v3 easier as a result of needing to release the cert changes. Is that correct?

@saperi22
Copy link
Copy Markdown
Collaborator Author

saperi22 commented Apr 1, 2026

I assume these are to make publishing v3 easier as a result of needing to release the cert changes. Is that correct?

v3.22.0 was already released. These were the changes that were used to release. Since the convention is that 3.x is the latest released, I want to merge the changes that were made in.

@saperi22 saperi22 changed the title 3.x publish 3.22.0 publish changes Apr 1, 2026
saralvasquez
saralvasquez approved these changes Apr 1, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@saralvasquez saralvasquez left a comment

Choose a reason for hiding this comment

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

I think this looks alright, although I wasn't around for publishing the last release so I'll defer to Ana

@saperi22 saperi22 merged commit b9d70f5 into 3.x Apr 1, 2026
@saperi22 saperi22 deleted the 3.x-publish branch April 1, 2026 23:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@noguier noguier noguier left review comments

@saralvasquez saralvasquez saralvasquez approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@saperi22 @saralvasquez @noguier