8000 chore: Prepare release 4.1.6 by fsbraun · Pull Request #8202 · django-cms/django-cms · GitHub
[go: up one dir, main page]

Skip to content

chore: Prepare release 4.1.6 #8202

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

Merged
merged 13 commits into from
Apr 22, 2025
Merged

chore: Prepare release 4.1.6 #8202

merged 13 commits into from
Apr 22, 2025

Conversation

fsbraun
Copy link
Member
@fsbraun fsbraun commented Apr 22, 2025

Description

Prepare release 4.1.6 fixing a temporary issue with django 5.2 (to be fixed in django 5.2.1).

Related resources

  • #...
  • #...

Checklist

  • I have opened this pull request against main
  • I have added or modified the tests when changing logic
  • I have followed the conventional commits guidelines to add meaningful information into the changelog
  • I have read the contribution guidelines and I have joined the channel #pr-reviews on our Discord Server to find a “pr review buddy” who is going to review my pull request.

Summary by Sourcery

Prepare release 4.1.6 to address a temporary issue with Django 5.2

Bug Fixes:

  • Update version number from 4.1.5 to 4.1.6 across various files

Chores:

  • Update static asset references to use version 4.1.6

Copy link
Contributor
sourcery-ai bot commented Apr 22, 2025

Reviewer's Guide by Sourcery

This pull request prepares the release 4.1.6, which includes updating the version number, icon font URLs, CSS files, javascript files, translation files, changelog, and adding a placeholder upgrade guide.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Updated the version number in the __init__.py file.
  • Changed the __version__ variable from '4.1.5' to '4.1.6'.
cms/__init__.py
Updated the icon font URLs in the _iconography.scss file.
  • Updated the font URLs to point to the '4.1.6' directory.
cms/static/cms/sass/components/_iconography.scss
Updated the CSS files to reflect the new version number.
  • Renamed the cms.admin.css, cms.base.css, and cms.pagetree.css files from the '4.1.5' directory to the '4.1.6' directory.
  • Updated the font URLs within the CSS files to point to the '4.1.6' directory.
  • Updated the image URLs within the CSS files to point to the '4.1.6' directory.
cms/static/cms/css/4.1.5/cms.admin.css
cms/static/cms/css/4.1.5/cms.base.css
cms/static/cms/css/4.1.5/cms.pagetree.css
cms/static/cms/css/4.1.5/cms.welcome.css
Updated the bundle admin pagetree javascript file to reflect the new version number.
  • Renamed the bundle.admin.pagetree.min.js file from the '4.1.5' directory to the '4.1.6' directory.
cms/static/cms/js/dist/4.1.5/bundle.admin.pagetree.min.js
Added a placeholder upgrade guide for version 4.1.6.
  • Created a new 4.1.6.rst file in the docs/upgrade/ directory.
docs/upgrade/4.1.6.rst
Updated the changelog to include the new release.
  • Updated the CHANGELOG.rst file.
CHANGELOG.rst
Updated the translation files.
  • Updated the django.po file in the cms/locale/zh_CN/LC_MESSAGES/ directory.
cms/locale/zh_CN/LC_MESSAGES/django.po
Updated the index file in the docs/upgrade directory.
  • Updated the index.rst file in the docs/upgrade/ directory.
docs/upgrade/index.rst

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

👋 Hi there!

Please remember to MERGE COMMIT pull requests from develop or develop-4!

Do not SQUASH commits to preserve history for the changelog.

@fsbraun fsbraun changed the title Release/build chore: Prepare release 4.1.6 Apr 22, 2025
Copy link
Contributor
@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @fsbraun - I've reviewed your changes - here's some feedback:

Overall Comments:

  • This looks like a standard release PR, but it's worth double-checking that the version number in cms/__init__.py is updated correctly.
Here's what I looked at during the review
  • 🟡 General issues: 4 issues found
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Complexity: all looks good
  • 🟢 Documentation: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Copy link

👋 Hi there!

Please remember to MERGE COMMIT pull requests from develop or develop-4!

Do not SQUASH commits to preserve history for the changelog.

@fsbraun fsbraun requested a review from vinitkumar April 22, 2025 19:42
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Copy link

👋 Hi there!

Please remember to MERGE COMMIT pull requests from develop or develop-4!

Do not SQUASH commits to preserve history for the changelog.

1 similar comment
Copy link

👋 Hi there!

Please remember to MERGE COMMIT pull requests from develop or develop-4!

Do not SQUASH commits to preserve history for the changelog.

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Copy link

👋 Hi there!

Please remember to MERGE COMMIT pull requests from develop or develop-4!

Do not SQUASH commits to preserve history for the changelog.

Copy link

👋 Hi there!

Please remember to MERGE COMMIT pull requests from develop or develop-4!

Do not SQUASH commits to preserve history for the changelog.

@fsbraun fsbraun merged commit a0fee5a into release/4.1.x Apr 22, 2025
93 checks passed
@fsbraun fsbraun deleted the release/build branch April 22, 2025 20:23
@fsbraun fsbraun restored the release/build branch April 22, 2025 20:23
@github-actions github-actions bot deleted the release/build branch May 6, 2025 09:21
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.

2 participants
0