manoelhc / test-actions

Test actions
MIT License
1 stars 2 forks source link

chore(deps): bump sqlalchemy from 2.0.30 to 2.0.31 #101

Closed dependabot[bot] closed 3 weeks ago

dependabot[bot] commented 3 weeks ago

Bumps sqlalchemy from 2.0.30 to 2.0.31.

Release notes

Sourced from sqlalchemy's releases.

2.0.31

Released: June 18, 2024

general

  • [general] [bug] Set up full Python 3.13 support to the extent currently possible, repairing issues within internal language helpers as well as the serializer extension module.

    References: #11417

orm

  • [orm] [usecase] Added missing parameter _orm.with_polymorphic.name that allows specifying the name of returned _orm.AliasedClass.

    References: #11361

  • [orm] [bug] Fixed issue where a MetaData collection would not be serializable, if an Enum or Boolean datatype were present which had been adapted. This specific scenario in turn could occur when using the Enum or Boolean within ORM Annotated Declarative form where type objects frequently get copied.

    References: #11365

  • [orm] [bug] Fixed issue where the _orm.selectinload() and _orm.subqueryload() loader options would fail to take effect when made against an inherited subclass that itself included a subclass-specific _orm.Mapper.with_polymorphic setting.

    References: #11446

  • [orm] [bug] Fixed very old issue involving the _orm.joinedload.innerjoin parameter where making use of this parameter mixed into a query that also included joined eager loads along a self-referential or other cyclical relationship, along with complicating factors like inner joins added for secondary tables and such, would have the chance of splicing a particular inner join to the wrong part of the query. Additional state has been added to the internal method that does this splice to make a better decision as to where splicing should proceed.

    References: #11449

  • [orm] [bug] [regression] Fixed bug in ORM Declarative where the __table__ directive could not be declared as a class function with _orm.declared_attr() on a superclass, including an __abstract__ class as well as coming from the

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
coderabbitai[bot] commented 3 weeks ago

[!IMPORTANT]

Review skipped

Ignore keyword(s) in the title.

Ignored keywords (1) * chore(deps):

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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 - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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 generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@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 as 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. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
deepsource-io[bot] commented 3 weeks ago

Here's the code health analysis summary for commits 31eec54..d1ce8d6. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource Python LogoPython✅ SuccessView Check ↗
DeepSource Test coverage LogoTest coverage✅ SuccessView Check ↗

Code Coverage Report

MetricAggregatePython
Branch Coverage87.9%87.9%
Condition Coverage87.9%87.9%
Composite Coverage96.2%96.2%
Line Coverage97.5%97.5%

💡 If you’re a repository administrator, you can configure the quality gates from the settings.
socket-security[bot] commented 3 weeks ago

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
pypi/sqlalchemy@2.0.31 environment, eval, filesystem, network, shell, unsafe 0 61.3 MB CaselIT

🚮 Removed packages: pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30, pypi/sqlalchemy@2.0.30

View full report↗︎

github-actions[bot] commented 3 weeks ago

Tag v0.20.0 (branch: main, SHA: 58bed6d) Added.

github-actions[bot] commented 3 weeks ago

Qodana Community for Python

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report To be able to view the detailed Qodana report, you can either: - Register at [Qodana Cloud](https://qodana.cloud/) and [configure the action](https://github.com/jetbrains/qodana-action#qodana-cloud) - Use [GitHub Code Scanning with Qodana](https://github.com/jetbrains/qodana-action#github-code-scanning) - Host [Qodana report at GitHub Pages](https://github.com/JetBrains/qodana-action/blob/3a8e25f5caad8d8b01c1435f1ef7b19fe8b039a0/README.md#github-pages) - Inspect and use `qodana.sarif.json` (see [the Qodana SARIF format](https://www.jetbrains.com/help/qodana/qodana-sarif-output.html#Report+structure) for details) To get `*.log` files or any other Qodana artifacts, run the action with `upload-result` option set to `true`, so that the action will upload the files as the job artifacts: ```yaml - name: 'Qodana Scan' uses: JetBrains/qodana-action@v2024.1.5 with: upload-result: true ```
Contact Qodana team Contact us at [qodana-support@jetbrains.com](mailto:qodana-support@jetbrains.com) - Or via our issue tracker: https://jb.gg/qodana-issue - Or share your feedback: https://jb.gg/qodana-discussions
codacy-production[bot] commented 3 weeks ago

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
:white_check_mark: +0.00% (target: -1.00%) :white_check_mark:
Coverage variation details | | Coverable lines | Covered lines | Coverage | | ------------- | ------------- | ------------- | ------------- | | Common ancestor commit (31eec547f7c9c94a49c06edb7878ad8b6925df18) | 407 | 397 | 97.54% | | | Head commit (d1ce8d617b55498cfd02dcd6b4fc11dc1025c6ce) | 407 (+0) | 397 (+0) | 97.54% (**+0.00%**) | **Coverage variation** is the difference between the coverage for the head and common ancestor commits of the pull request branch: ` - `
Diff coverage details | | Coverable lines | Covered lines | Diff coverage | | ------------- | ------------- | ------------- | ------------- | | Pull request (#101) | 0 | 0 | **∅ (not applicable)** | **Diff coverage** is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: `/ * 100%`

See your quality gate settings    Change summary preferences


:rocket: Don’t miss a bit, follow what’s new on Codacy.

Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more

sonarcloud[bot] commented 3 weeks ago

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

codecov[bot] commented 3 weeks ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.81%. Comparing base (31eec54) to head (d1ce8d6).

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #101 +/- ## ======================================= Coverage 97.81% 97.81% ======================================= Files 10 10 Lines 411 411 Branches 76 76 ======================================= Hits 402 402 Misses 9 9 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.