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

chore(main): release 0.17.0 #808

Merged
merged 1 commit into from
Nov 5, 2024
Merged

Conversation

dreulavelle
Copy link
Member

@dreulavelle dreulavelle commented Oct 21, 2024

🤖 I have created a release beep boop

0.17.0 (2024-11-05)

Features

  • add manual torrent adding (#785) (acb22ce)
  • Add Most Wanted items from Trakt (#777) (325df42)
  • add rate limiting tests and update dependencies (#857) (27c8534)
  • auth bearer authentication (0de32fd)
  • database migrations, so long db resets (#858) (14e818f)
  • enhance session management and event processing (#842) (13aa94e)
  • filesize filter (d2f8374)
  • integrate dependency injection with kink library (#859) (ed5fb2c)
  • requests second pass (#848) (d41c2ff)
  • stream management endpoints (d75149e)
  • we now server sse via /stream (efbc471)

Bug Fixes

  • add default value for API_KEY (bc6ff28)
  • add python-dotenv to load .env variables (65a4aec)
  • correct type hint for incomplete_retries in StatsResponse (#839) (f91ffec)
  • duplicate item after scraping for media that isn't in the database already (#834) (4d7ac8d)
  • ensure selected files are stored in session during manual selection (#841) (86e6fd0)
  • files sometimes not found in mount (02b7a81)
  • future cancellation resulted in reset, retry endpoints fialing (#817) (19cedc8)
  • handle removal of nested media items in remove_item function (#840) (2096a4e)
  • hotfix blacklist active stream (8631008)
  • invalid rd instant availibility call if no infohashes should be checked (#843) (19cf38f)
  • jackett again - my bad (#860) (703ad33)
  • MediaFusion scraper. (#850) (0bbde7d)
  • mediafusion sometimes throwing error when parsing response (#844) (9c093ac)
  • misleading message when manually adding a torrent (#822) (18cfa3b)
  • overseerr outputting items without imdbid's (45528a9)
  • remove accidental cache enablement (877ffec)
  • retry api now resets scraped_at (#816) (2676fe8)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

Release Notes for Version 0.17.0

  • New Features

    • Manual torrent adding functionality.
    • Integration of "Most Wanted" items from Trakt.
    • Bearer authentication for API access.
    • New filesize filter feature.
    • Stream management endpoints and server-sent events via /stream.
  • Bug Fixes

    • Resolved issues with duplicate items, session storage, and file retrieval.
    • Fixed misleading messages and improved handling of media items.

These updates enhance user experience and system reliability.

@dreulavelle dreulavelle force-pushed the release-please--branches--main branch 6 times, most recently from 471bb6f to 0df4cf2 Compare October 26, 2024 12:34
@dreulavelle
Copy link
Member Author

Just adding a note, when this gets released we need to update the wiki for Overseerr and make an announcement of its change too.

@dreulavelle dreulavelle force-pushed the release-please--branches--main branch 3 times, most recently from 183b0a9 to 7c10a9d Compare October 26, 2024 19:36
@Gaisberg
Copy link
Collaborator

Just adding a note, when this gets released we need to update the wiki for Overseerr and make an announcement of its change too.

And also api path changes for advanced users along with api_key requirements

@davidemarcoli
Copy link
Collaborator

Just adding a note, when this gets released we need to update the wiki for Overseerr and make an announcement of its change too.

And the filesize filter settings.

@dreulavelle dreulavelle force-pushed the release-please--branches--main branch 5 times, most recently from af808fe to 602176b Compare November 2, 2024 10:03
@dreulavelle dreulavelle force-pushed the release-please--branches--main branch 7 times, most recently from 831f46a to 3b57fff Compare November 4, 2024 05:13
@dreulavelle
Copy link
Member Author

@coderabbitai review

Copy link
Contributor

coderabbitai bot commented Nov 4, 2024

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link
Contributor

coderabbitai bot commented Nov 4, 2024

Walkthrough

The changes in this pull request include updates to the changelog and the pyproject.toml file. The changelog details the release notes for version 0.17.0, highlighting new features such as manual torrent adding, integration with Trakt, and enhancements in session management. It also lists numerous bug fixes. The pyproject.toml file reflects the project version increment to 0.17.0 and updates to various dependencies, ensuring compatibility with newer library versions.

Changes

File Change Summary
CHANGELOG.md Updated to include release notes for version 0.17.0, detailing new features (manual torrent adding, Trakt integration, API bearer authentication, etc.) and bug fixes.
pyproject.toml Updated project version to 0.17.0; modified dependencies: regex, sqlalchemy, psutil, python-dotenv updated; added requests-ratelimiter, requests-cache, and httpx.

Poem

In the meadow, changes bloom,
New features chase away the gloom.
With torrents added, streams now flow,
Bugs are fixed, and watch us grow!
A hop, a skip, a joyful cheer,
Version 0.17.0 is finally here! 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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 resolve resolve all the CodeRabbit review comments.
  • @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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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

🧹 Outside diff range and nitpick comments (3)
pyproject.toml (2)

Line range hint 59-59: Consider consolidating pytest dependencies.

The pytest dependency is specified in both [tool.poetry.group.dev.dependencies] and [tool.poetry.group.test.dependencies] with the same version (^8.3.2). Consider maintaining it in just one location to avoid potential version conflicts in the future.

[tool.poetry.group.dev.dependencies]
- pytest = "^8.3.2"
pytest-mock = "^3.14.0"

Also applies to: 76-76


Line range hint 1-77: Document new dependency requirements in README.

Given the significant changes in dependencies and the addition of new features (manual torrent adding, Trakt integration, etc.), consider updating the project's README or documentation to reflect:

  1. Minimum Python version requirements
  2. New optional dependencies for specific features
  3. Configuration requirements for new features (especially bearer authentication and rate limiting)
CHANGELOG.md (1)

8-14: Consider adding more descriptive details for some features.

While the feature entries follow the conventional format, some could benefit from more descriptive messages to better convey the impact and scope of changes. For example:

  • "stream management endpoints" could specify which endpoints were added
  • "we now server sse via /stream" has a typo ("server" -> "serve") and could explain the purpose/benefit of SSE

Apply this diff to fix the typo:

-* we now server sse via /stream ([efbc471](https://github.com/rivenmedia/riven/commit/efbc471e4f4429c098df2a601b3f3c42b98afbb7))
+* we now serve SSE via /stream ([efbc471](https://github.com/rivenmedia/riven/commit/efbc471e4f4429c098df2a601b3f3c42b98afbb7))
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 0d31e41 and 3b57fff.

📒 Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • pyproject.toml (1 hunks)
🔇 Additional comments (5)
pyproject.toml (3)

3-3: Version bump looks good!

The version increment to 0.17.0 aligns with the significant feature additions and changes described in the PR objectives.


Line range hint 24-24: Verify SQLAlchemy 2.0 compatibility.

The update to SQLAlchemy 2.0 is a major version change that might introduce breaking changes. The PR objectives don't mention database-related changes, so we should verify the compatibility.

#!/bin/bash
# Description: Check for SQLAlchemy-specific code patterns that might need updates for 2.0

echo "Checking for potential SQLAlchemy compatibility issues..."

# Look for common SQLAlchemy patterns that changed in 2.0
rg -l "from sqlalchemy import *" || echo "No wildcard imports found (good!)"

# Check for session usage patterns that changed in 2.0
ast-grep --pattern 'Session.query($$$)' || echo "No legacy Session.query usage found (good!)"

# Check for engine/connection patterns
ast-grep --pattern 'create_engine($$$, future=True)' || echo "No legacy engine creation found"

Consider documenting any required SQLAlchemy migration steps in the release notes if breaking changes are identified.

Also applies to: 33-33, 36-36, 37-37


Line range hint 52-53: Verify compatibility of new dependencies.

The addition of rate limiting and caching libraries aligns with the PR objectives for improved session management. However, let's verify the compatibility of these versions with the project's Python version requirement (^3.11).

Also applies to: 65-65

✅ Verification successful

The previous script didn't provide the Python version requirements as intended. Let me try a different approach to verify the compatibility.


All new dependencies are compatible with project's Python requirement

The project requires Python ^3.11, and all new dependencies support this version:

  • httpx 0.27.0: requires Python >=3.8
  • requests-ratelimiter 0.7.0: requires Python >=3.7,<4.0
  • requests-cache 1.2.1: requires Python >=3.8
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check minimum Python version requirements for new dependencies

echo "Checking Python version requirements for new dependencies..."
for pkg in "requests-ratelimiter==0.7.0" "requests-cache==1.2.1" "httpx==0.27.0"; do
    pip debug --verbose --index-url https://pypi.org/simple required-python-version "$pkg"
done

Length of output: 560


Script:

#!/bin/bash
# Check if pyproject.toml contains Python version constraint
echo "Python version requirement in pyproject.toml:"
rg "python\s*=" pyproject.toml

# Check dependencies' metadata
echo -e "\nChecking httpx metadata:"
curl -s https://pypi.org/pypi/httpx/0.27.0/json | jq '.info.requires_python'

echo -e "\nChecking requests-ratelimiter metadata:"
curl -s https://pypi.org/pypi/requests-ratelimiter/0.7.0/json | jq '.info.requires_python'

echo -e "\nChecking requests-cache metadata:"
curl -s https://pypi.org/pypi/requests-cache/1.2.1/json | jq '.info.requires_python'

Length of output: 675

CHANGELOG.md (2)

3-4: LGTM! Version header follows conventional changelog format.

The version header correctly includes:

  • Version number with link to GitHub compare view
  • Release date in parentheses

19-33: LGTM! Bug fixes are well documented.

The bug fixes section:

  • Follows conventional commit format
  • Includes links to issues and commit hashes
  • Provides clear descriptions of what was fixed

@dreulavelle dreulavelle force-pushed the release-please--branches--main branch from 3b57fff to 0ba69f1 Compare November 4, 2024 10:57
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

🧹 Outside diff range and nitpick comments (2)
CHANGELOG.md (2)

8-14: Maintain consistent capitalization and punctuation in feature entries.

Some entries start with lowercase letters while others start with uppercase. For better readability and consistency:

  1. Start each entry with a capital letter
  2. End each entry with a period
  3. Use consistent verb tense (present tense preferred)

Apply this diff to fix the inconsistencies:

-* add manual torrent adding ([#785](https://github.com/rivenmedia/riven/issues/785)) ([acb22ce](https://github.com/rivenmedia/riven/commit/acb22ce9bb54a09a542e1a587181eb731700243e))
-* Add Most Wanted items from Trakt ([#777](https://github.com/rivenmedia/riven/issues/777)) ([325df42](https://github.com/rivenmedia/riven/commit/325df42989e8d6d841ab625284c54d78b9dc02d1))
-* auth bearer authentication ([0de32fd](https://github.com/rivenmedia/riven/commit/0de32fd9e7255c8c91aae4cecb428cabe180aea9))
-* enhance session management and event processing ([#842](https://github.com/rivenmedia/riven/issues/842)) ([13aa94e](https://github.com/rivenmedia/riven/commit/13aa94e5587661770d385d634fa1a3cef9b0d882))
-* filesize filter ([d2f8374](https://github.com/rivenmedia/riven/commit/d2f8374ae95fc763842750a67d1d9b9f3c545a8d))
-* stream management endpoints ([d75149e](https://github.com/rivenmedia/riven/commit/d75149eb5b246bf7312ddb3d3fac85417e2cb215))
-* we now server sse via /stream ([efbc471](https://github.com/rivenmedia/riven/commit/efbc471e4f4429c098df2a601b3f3c42b98afbb7))
+* Adds manual torrent adding functionality. ([#785](https://github.com/rivenmedia/riven/issues/785)) ([acb22ce](https://github.com/rivenmedia/riven/commit/acb22ce9bb54a09a542e1a587181eb731700243e))
+* Adds Most Wanted items from Trakt. ([#777](https://github.com/rivenmedia/riven/issues/777)) ([325df42](https://github.com/rivenmedia/riven/commit/325df42989e8d6d841ab625284c54d78b9dc02d1))
+* Implements bearer authentication. ([0de32fd](https://github.com/rivenmedia/riven/commit/0de32fd9e7255c8c91aae4cecb428cabe180aea9))
+* Enhances session management and event processing. ([#842](https://github.com/rivenmedia/riven/issues/842)) ([13aa94e](https://github.com/rivenmedia/riven/commit/13aa94e5587661770d385d634fa1a3cef9b0d882))
+* Adds filesize filter functionality. ([d2f8374](https://github.com/rivenmedia/riven/commit/d2f8374ae95fc763842750a67d1d9b9f3c545a8d))
+* Adds stream management endpoints. ([d75149e](https://github.com/rivenmedia/riven/commit/d75149eb5b246bf7312ddb3d3fac85417e2cb215))
+* Implements Server-Sent Events (SSE) via /stream endpoint. ([efbc471](https://github.com/rivenmedia/riven/commit/efbc471e4f4429c098df2a601b3f3c42b98afbb7))

19-33: Maintain consistent capitalization and punctuation in bug fix entries.

Similar to the feature entries, the bug fix entries should follow consistent formatting.

Apply this diff to fix the inconsistencies:

-* add default value for API_KEY ([bc6ff28](https://github.com/rivenmedia/riven/commit/bc6ff28ff5b1d1632f2dd2ca64743c4012ccc396))
-* add python-dotenv to load .env variables ([65a4aec](https://github.com/rivenmedia/riven/commit/65a4aec275a1f7768a77ef0227d6fb402f9a8612))
-* correct type hint for incomplete_retries in StatsResponse ([#839](https://github.com/rivenmedia/riven/issues/839)) ([f91ffec](https://github.com/rivenmedia/riven/commit/f91ffece2a70af71967903847068642e58a4f51c))
+* Adds default value for API_KEY. ([bc6ff28](https://github.com/rivenmedia/riven/commit/bc6ff28ff5b1d1632f2dd2ca64743c4012ccc396))
+* Adds python-dotenv to load .env variables. ([65a4aec](https://github.com/rivenmedia/riven/commit/65a4aec275a1f7768a77ef0227d6fb402f9a8612))
+* Corrects type hint for incomplete_retries in StatsResponse. ([#839](https://github.com/rivenmedia/riven/issues/839)) ([f91ffec](https://github.com/rivenmedia/riven/commit/f91ffece2a70af71967903847068642e58a4f51c))
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3b57fff and 0ba69f1.

📒 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 comments (1)
CHANGELOG.md (1)

3-4: LGTM!

The version header follows semantic versioning format and includes the correct GitHub compare URL.

@dreulavelle dreulavelle force-pushed the release-please--branches--main branch 4 times, most recently from 4c436cc to 39f916e Compare November 5, 2024 11: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

🧹 Outside diff range and nitpick comments (1)
CHANGELOG.md (1)

6-16: Consider improving feature descriptions and fixing typo.

While the features section is well-structured with proper links and commit hashes, consider:

  1. Making some feature titles more descriptive:
    • "requests second pass" could better explain the changes
  2. Fixing the typo:
    • "we now server sse" should be "we now serve SSE"
🧰 Tools
🪛 LanguageTool

[uncategorized] ~10-~10: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...9e8d6d841ab625284c54d78b9dc02d1)) * add rate limiting tests and update dependencies ([#857](h...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4c436cc and 39f916e.

📒 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

[uncategorized] ~10-~10: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...9e8d6d841ab625284c54d78b9dc02d1)) * add rate limiting tests and update dependencies ([#857](h...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

🔇 Additional comments (2)
CHANGELOG.md (2)

3-5: LGTM! Version header follows best practices.

The version header is well-formatted with:

  • Semantic version number (0.17.0)
  • GitHub compare link
  • ISO date format

19-36: LGTM! Bug fixes are well-documented.

The bug fixes section is comprehensive and follows best practices:

  • Clear descriptions of the resolved issues
  • Proper linking to GitHub issues and commits
  • Good organization of the fixes

@dreulavelle dreulavelle force-pushed the release-please--branches--main branch from 39f916e to 10dbc83 Compare November 5, 2024 13: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

🧹 Outside diff range and nitpick comments (1)
CHANGELOG.md (1)

6-17: Consider hyphenating the compound adjective.

The features are well-documented with proper references. However, consider hyphenating "rate limiting" to "rate-limiting" in the feature description as it's used as a compound adjective.

Apply this diff:

-* add rate limiting tests and update dependencies ([#857](https://github.com/rivenmedia/riven/issues/857)) ([27c8534](https://github.com/rivenmedia/riven/commit/27c8534f3084404f80e6bf8fc01b1be0b9d98ad8))
+* add rate-limiting tests and update dependencies ([#857](https://github.com/rivenmedia/riven/issues/857)) ([27c8534](https://github.com/rivenmedia/riven/commit/27c8534f3084404f80e6bf8fc01b1be0b9d98ad8))
🧰 Tools
🪛 LanguageTool

[uncategorized] ~10-~10: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...9e8d6d841ab625284c54d78b9dc02d1)) * add rate limiting tests and update dependencies ([#857](h...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 39f916e and 10dbc83.

📒 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

[uncategorized] ~10-~10: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...9e8d6d841ab625284c54d78b9dc02d1)) * add rate limiting tests and update dependencies ([#857](h...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

🔇 Additional comments (2)
CHANGELOG.md (2)

3-5: LGTM!

The version header follows the standard changelog format with proper version number, GitHub comparison link, and release date.


20-37: LGTM!

The bug fixes are well-documented with proper references and clear descriptions.

@dreulavelle dreulavelle force-pushed the release-please--branches--main branch from 10dbc83 to 4901381 Compare November 5, 2024 14:46
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

🧹 Outside diff range and nitpick comments (2)
CHANGELOG.md (2)

10-10: Consider adding a hyphen for consistency.

The entry "add rate limiting tests" should use a hyphen for the compound adjective.

-* add rate limiting tests and update dependencies ([#857](https://github.com/rivenmedia/riven/issues/857)) ([27c8534](https://github.com/rivenmedia/riven/commit/27c8534f3084404f80e6bf8fc01b1be0b9d98ad8))
+* add rate-limiting tests and update dependencies ([#857](https://github.com/rivenmedia/riven/issues/857)) ([27c8534](https://github.com/rivenmedia/riven/commit/27c8534f3084404f80e6bf8fc01b1be0b9d98ad8))
🧰 Tools
🪛 LanguageTool

[uncategorized] ~10-~10: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...9e8d6d841ab625284c54d78b9dc02d1)) * add rate limiting tests and update dependencies ([#857](h...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


17-18: Consider adding more context to the stream endpoint entry.

The entry about Server-Sent Events (SSE) could benefit from additional context about its purpose and benefits.

-* we now server sse via /stream ([efbc471](https://github.com/rivenmedia/riven/commit/efbc471e4f4429c098df2a601b3f3c42b98afbb7))
+* we now serve Server-Sent Events (SSE) via /stream endpoint for real-time updates ([efbc471](https://github.com/rivenmedia/riven/commit/efbc471e4f4429c098df2a601b3f3c42b98afbb7))
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 10dbc83 and 4901381.

📒 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

[uncategorized] ~10-~10: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...9e8d6d841ab625284c54d78b9dc02d1)) * add rate limiting tests and update dependencies ([#857](h...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

🔇 Additional comments (1)
CHANGELOG.md (1)

3-39: LGTM! The changelog is well-structured and informative.

The changelog follows proper conventions with:

  • Clear semantic versioning
  • Proper categorization of changes
  • Consistent linking to issues and commits
🧰 Tools
🪛 LanguageTool

[uncategorized] ~10-~10: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...9e8d6d841ab625284c54d78b9dc02d1)) * add rate limiting tests and update dependencies ([#857](h...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

@dreulavelle dreulavelle force-pushed the release-please--branches--main branch from 4901381 to b0cd0ba Compare November 5, 2024 15:08
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

🧹 Outside diff range and nitpick comments (2)
CHANGELOG.md (2)

6-18: Consider adding more context to feature descriptions.

While the feature entries are well-formatted and include proper references, some entries could benefit from additional context about their impact:

  • "bearer authentication" - Consider mentioning the security benefits or changes required by users
  • "filesize filter" - Consider specifying the supported size ranges or use cases
  • "stream management endpoints" - Consider listing the key endpoints added
🧰 Tools
🪛 LanguageTool

[uncategorized] ~10-~10: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...9e8d6d841ab625284c54d78b9dc02d1)) * add rate limiting tests and update dependencies ([#857](h...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


21-39: Maintain consistency in commit message style.

While most bug fix entries start with a verb in present tense (e.g., "add", "correct", "ensure"), some entries use past tense or different formats:

  • "jackett again - my bad" could be more descriptive
  • "MediaFusion scraper." could specify what was fixed
  • "files sometimes not found in mount" could start with a verb

Consider standardizing all commit messages to use present tense and be more descriptive.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4901381 and b0cd0ba.

📒 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

[uncategorized] ~10-~10: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...9e8d6d841ab625284c54d78b9dc02d1)) * add rate limiting tests and update dependencies ([#857](h...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

🔇 Additional comments (1)
CHANGELOG.md (1)

3-5: LGTM! Header follows standard changelog format.

The release header is well-structured with version, date, and compare link.

@iPromKnight iPromKnight merged commit fd5c726 into main Nov 5, 2024
2 checks passed
@iPromKnight iPromKnight deleted the release-please--branches--main branch November 5, 2024 16:44
@dreulavelle
Copy link
Member 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.

4 participants