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/4.5.0 #242

Merged
merged 7 commits into from
Jul 15, 2024
Merged

Release/4.5.0 #242

merged 7 commits into from
Jul 15, 2024

Conversation

jeffpaul
Copy link
Member

@jeffpaul jeffpaul commented Jul 11, 2024

Description of the Change

Version bump and prep for the 4.5.0 release.

Closes #241 #237.

How to test the Change

Verify all file changes look accurate.

Changelog Entry

n/a

Credits

Props @jeffpaul.

Checklist:

  • I agree to follow this project's Code of Conduct.
  • I have updated the documentation accordingly.
  • I have added tests to cover my change.
  • All new and existing tests pass.

@jeffpaul jeffpaul added this to the 4.5.0 milestone Jul 11, 2024
@jeffpaul jeffpaul self-assigned this Jul 11, 2024
@jeffpaul
Copy link
Member Author

Blocking until #240 is merged.

@jeffpaul jeffpaul linked an issue Jul 11, 2024 that may be closed by this pull request
@jeffpaul
Copy link
Member Author

Oddly not seeing the changes from #240 after that merge from develop. Holding off on further release work until we can ensure things will merge properly to develop (and then to trunk for the release).

@rickalee
Copy link
Collaborator

@jeffpaul Seeing get_azure_storage_override_container_path and constant in develop. https://github.com/search?q=repo:10up/windows-azure-storage%20get_azure_storage_override_container_path&type=code

@dkotter dkotter merged commit 9024dff into develop Jul 15, 2024
8 checks passed
@dkotter dkotter deleted the release/4.5.0 branch July 15, 2024 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Release version 4.5.0 The plugin hasn't been tested with an upcoming version of WordPress
3 participants