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 v4.1.0 #1558

Conversation

edwardchalstrey1
Copy link
Contributor

@edwardchalstrey1 edwardchalstrey1 commented Aug 16, 2023

✅ Checklist

  • You have given your pull request a meaningful title (e.g. Enable foobar integration rather than 515 foobar).
  • You are targeting the appropriate branch. If you're not certain which one this is, it should be develop.
  • Your branch is up-to-date with the target branch (it probably was when you started, but it may have changed since then).
  • You have marked this pull request as a draft and added '[WIP]' to the title if needed (if you're not yet ready to merge).
  • You have formatted your code using appropriate automated tools (for example ./tests/AutoFormat_Powershell.ps1 -TargetPath <path to file or directory> for Powershell).

⤴️ Summary

All changes from the 4.1.0 release

🌂 Related issues

Closes #1544

🔬 Tests

See #1544

jemrobinson and others added 30 commits March 13, 2023 15:53
…ute/reset-package-cache

Fix allowlist generation
…ute/fix-allowlist-prs

Fix incorrect logic around automated PR creation
…ute/package-allowlist-updates

Update PyPI and CRAN allow lists
…dd-servicebus

Add new servicebus endpoints for self-service password reset
…ute/package-allowlist-updates

Update PyPI and CRAN allow lists
jemrobinson and others added 20 commits July 26, 2023 11:20
…ute/srd-package-versions

Update SRD package versions
…ute/update-package-resolution

Use pip-compile for package resolution
…ip-tools-executable

Add pip-tools to NON_IMPORTABLE_PACKAGES
Add May 2023 DSG to versioning
…ute/add-may-dsg

Add May 2023 DSG to versioning
…elease-v4.1.0

Release v4.1.0 cloud init changes
Copy link
Member

@JimMadge JimMadge left a comment

Choose a reason for hiding this comment

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

Hold until we have checked the deployment logs and security checklist.

@JimMadge JimMadge changed the title Release v4.1.0 changes Release v4.1.0 Aug 17, 2023
@edwardchalstrey1 edwardchalstrey1 marked this pull request as draft August 21, 2023 09:43
@jemrobinson
Copy link
Member

@craddm : are you using this branch on @edwardchalstrey1's repo or the release-v4.1.0 branch on this repo? If the latter, I think we should close this PR and open a new one from the branch you're using.

@craddm
Copy link
Contributor

craddm commented Aug 29, 2023

Yes, I'm using the branch from the main repo (which was up-to-date with Ed's) so best close this and I'll do a new one.

@jemrobinson
Copy link
Member

Superceded by new PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants