Skip to content

chore(main): release 1.2.0 #247

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 1 commit into from
Apr 9, 2025
Merged

Conversation

snakemake-bot
Copy link
Contributor

@snakemake-bot snakemake-bot commented Mar 27, 2025

🤖 I have created a release beep boop

1.2.0 (2025-04-04)

Features

Bug Fixes

  • account and partition settings corrected (#249) (e7a248f)
  • case insensitive matching of declared slurm account (#244) (dc9a4fd)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • New Features

    • Introduced a new QoS resource.
  • Bug Fixes

    • Resolved issues with account and partition settings.
    • Improved case insensitive matching for account names.
  • Chores

    • Updated the package version to 1.2.0.

Copy link
Contributor

coderabbitai bot commented Mar 27, 2025

Walkthrough

This PR updates the Snakemake executor plugin for SLURM from version 1.1.0 to 1.2.0. It adds a new version entry in the CHANGELOG.md dated April 4, 2025, documenting the addition of a new 'qos' resource (issue #241, commit c8cdfc4) and includes a bug fix for corrected account and partition settings (issue #249, commit e7a248f). The package version is also updated in the pyproject.toml file.

Changes

File(s) Change Summary
CHANGELOG.md Added version entry for v1.2.0 (2025-04-04) with a new 'qos' resource (issue #241, commit c8cdfc4), new bug fix for account and partition settings (issue #249, commit e7a248f), and reiterated bug fix for case insensitive matching of declared SLURM accounts (issue #244, commit dc9a4fd)
pyproject.toml Updated package version from 1.1.0 to 1.2.0

Possibly related PRs

Suggested labels

autorelease: tagged

Suggested reviewers

  • cmeesters
  • johanneskoester

Poem

Hoppy rabbit here with a gleeful cheer,
Bumping versions as the update draws near.
A 'qos' resource hops into the fray,
With SLURM accounts matching, hip-hip-hooray!
I leap and I code with joy in my heart—
Each change is a treasure, a work of fine art!
(_/)


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
CHANGELOG.md (1)

6-8: Minor Language Suggestion
Consider hyphenating "case insensitive" to "case‐insensitive" for consistency with standard English style guidelines. This would ensure uniformity in technical documentation.

🧰 Tools
🪛 LanguageTool

[misspelling] ~8-~8: This word is normally spelled with a hyphen.
Context: ...v1.1.1) (2025-03-27) ### Bug Fixes * case insensitive matching of declared slurm account ([#...

(EN_COMPOUNDS_CASE_INSENSITIVE)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dc9a4fd and 0f4afba.

📒 Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • pyproject.toml (1 hunks)
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[misspelling] ~8-~8: This word is normally spelled with a hyphen.
Context: ...v1.1.1) (2025-03-27) ### Bug Fixes * case insensitive matching of declared slurm account ([#...

(EN_COMPOUNDS_CASE_INSENSITIVE)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: testing
🔇 Additional comments (2)
pyproject.toml (1)

1-3: Version Bump Verification
The version has been updated to "1.1.1" as expected for the release. This change correctly aligns with the PR objective and appears consistent with the project conventions.

CHANGELOG.md (1)

3-4: New Release Entry Added
The new version entry for 1.1.1, dated 2025-03-27, is well formatted and provides clear context for this release.

@snakemake-bot snakemake-bot changed the title chore(main): release 1.1.1 chore(main): release 1.2.0 Mar 31, 2025
@snakemake-bot snakemake-bot force-pushed the release-please--branches--main branch from 0f4afba to 0063c71 Compare March 31, 2025 09:42
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
CHANGELOG.md (1)

11-13: Bug Fix Entry Verified
The Bug Fixes section correctly reiterates the fix for case insensitive matching of declared Slurm accounts with the relevant issue ([#244]) and commit hash (dc9a4fd).
Suggestion: Consider hyphenating "case insensitive" to "case‐insensitive" to align with standard compound adjective styling.

🧰 Tools
🪛 LanguageTool

[misspelling] ~13-~13: This word is normally spelled with a hyphen.
Context: ...9789cb7058dde98013)) ### Bug Fixes * case insensitive matching of declared slurm account ([#...

(EN_COMPOUNDS_CASE_INSENSITIVE)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0f4afba and 0063c71.

📒 Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • pyproject.toml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • pyproject.toml
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[misspelling] ~13-~13: This word is normally spelled with a hyphen.
Context: ...9789cb7058dde98013)) ### Bug Fixes * case insensitive matching of declared slurm account ([#...

(EN_COMPOUNDS_CASE_INSENSITIVE)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: testing
🔇 Additional comments (2)
CHANGELOG.md (2)

3-4: New Version Header Added
The new version header for version 1.2.0 is formatted correctly with a proper comparison link and the accurate release date (2025-03-31) that aligns with the PR objectives.


6-8: Features Section Correctly Documented
The Features section clearly lists the new 'qos' resource with its corresponding issue ([#241]) and commit hash (c8cdfc4). This accurately reflects the new functionality introduced in this release.

@snakemake-bot snakemake-bot force-pushed the release-please--branches--main branch from 0063c71 to 1283fcc Compare March 31, 2025 12:05
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
CHANGELOG.md (2)

6-8: New Feature: "qos" Resource

The feature entry documenting the addition of the new 'qos' resource is clear and includes the relevant issue (#241) and commit reference. Consider adding a brief explanatory note about the purpose or impact of the 'qos' resource if not already covered in the documentation.


11-15: Bug Fixes Documentation Check

The bug fix entries are well detailed with proper issue references and commit hashes. However, on line 14, consider changing "case insensitive matching of declared slurm account" to "case‑insensitive matching of declared slurm account" to align with standard spelling conventions.

🧰 Tools
🪛 LanguageTool

[misspelling] ~14-~14: This word is normally spelled with a hyphen.
Context: ...8f4aeb50886535f13f5b8d4b56036951d87)) * case insensitive matching of declared slurm account ([#...

(EN_COMPOUNDS_CASE_INSENSITIVE)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0063c71 and 1283fcc.

📒 Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • pyproject.toml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • pyproject.toml
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[misspelling] ~14-~14: This word is normally spelled with a hyphen.
Context: ...8f4aeb50886535f13f5b8d4b56036951d87)) * case insensitive matching of declared slurm account ([#...

(EN_COMPOUNDS_CASE_INSENSITIVE)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: testing
🔇 Additional comments (1)
CHANGELOG.md (1)

3-4: New Version Entry for 1.2.0

The new version header for 1.2.0 and the corresponding date are well formatted and provide clear release context.

@snakemake-bot snakemake-bot force-pushed the release-please--branches--main branch from 1283fcc to f4b9551 Compare April 4, 2025 10:23
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
CHANGELOG.md (1)

11-15: Bug Fixes Section Documents Corrections with Clear References
The Bug Fixes section accurately reflects the corrections for account and partition settings ([#249]) as well as for case insensitive matching of declared Slurm accounts ([#244]).
Suggestion: Consider changing “case insensitive matching of declared slurm account” to “case‐insensitive matching of declared Slurm account” to conform with standard hyphenation and capitalization conventions.

🧰 Tools
🪛 LanguageTool

[misspelling] ~14-~14: This word is normally spelled with a hyphen.
Context: ...8f4aeb50886535f13f5b8d4b56036951d87)) * case insensitive matching of declared slurm account ([#...

(EN_COMPOUNDS_CASE_INSENSITIVE)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1283fcc and f4b9551.

📒 Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • pyproject.toml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • pyproject.toml
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[misspelling] ~14-~14: This word is normally spelled with a hyphen.
Context: ...8f4aeb50886535f13f5b8d4b56036951d87)) * case insensitive matching of declared slurm account ([#...

(EN_COMPOUNDS_CASE_INSENSITIVE)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: testing
🔇 Additional comments (2)
CHANGELOG.md (2)

3-4: Version Entry for 1.2.0 is Correctly Formatted
The new version entry for 1.2.0 follows the established format with a proper URL diff link and the correct release date, "2025-04-04".


6-9: Features Section Accurately Documents the 'qos' Resource
The Features section clearly states that a new 'qos' resource was added, referencing issue [#241] and the associated commit. This makes it straightforward for users to trace the change.

@cmeesters cmeesters self-requested a review April 9, 2025 12:29
@cmeesters cmeesters merged commit 89ed1dd into main Apr 9, 2025
7 checks passed
@cmeesters cmeesters deleted the release-please--branches--main branch April 9, 2025 12:30
@snakemake-bot
Copy link
Contributor Author

🤖 Created releases:

🌻

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

Successfully merging this pull request may close these issues.

2 participants