Skip to content

chore: Prepare release 2.1.2 #273

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 6 commits into from
Apr 25, 2025
Merged

chore: Prepare release 2.1.2 #273

merged 6 commits into from
Apr 25, 2025

Conversation

fsbraun
Copy link
Member

@fsbraun fsbraun commented Apr 5, 2025

Summary by Sourcery

Prepare release 2.1.2 by updating version number and refactoring djangocms_text initialization logic

Enhancements:

  • Simplify initialization logic for djangocms_text inline editable models

Chores:

  • Bump package version from 2.1.1 to 2.1.2

Copy link
Contributor

sourcery-ai bot commented Apr 5, 2025

Reviewer's Guide by Sourcery

This pull request prepares the release of version 2.1.2. It updates the version number in __init__.py and CHANGELOG.rst. Additionally, it modifies the component pool setup to ensure inline editable fields are correctly initialized when djangocms_text is installed, by reinitializing inline models to reflect newly discovered components.

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

File-Level Changes

Change Details Files
Updates the version number to 2.1.2.
  • Updates the version number in __init__.py.
  • Updates the version number in CHANGELOG.rst.
djangocms_frontend/__init__.py
CHANGELOG.rst
Reinitializes inline editable fields to reflect newly discovered components when djangocms_text is installed.
  • Removes a conditional check for inline model initialization.
  • Moves the inline model initialization to ensure it always runs when djangocms_text is installed.
djangocms_frontend/component_pool.py

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
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:

  • Consider adding a description to the pull request to provide more context.
Here's what I looked at during the review
  • 🟡 General issues: 1 issue 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.

Copy link

codecov bot commented Apr 5, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.68%. Comparing base (15eed03) to head (3a8f762).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #273   +/-   ##
=======================================
  Coverage   88.68%   88.68%           
=======================================
  Files         124      124           
  Lines        3366     3366           
  Branches      283      283           
=======================================
  Hits         2985     2985           
  Misses        264      264           
  Partials      117      117           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

fsbraun and others added 2 commits April 25, 2025 20:14
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
@fsbraun fsbraun merged commit cbaa073 into master Apr 25, 2025
33 of 34 checks passed
@fsbraun fsbraun deleted the fix/racing-condition branch April 25, 2025 18:16
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.

1 participant