Skip to content

Update dependency syrupy to v5 - #727

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/syrupy-5.x
Open

Update dependency syrupy to v5#727
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/syrupy-5.x

Conversation

@renovate

@renovate renovate Bot commented Sep 29, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
syrupy ^4.6.1^5.0.0 age confidence

Release Notes

syrupy-project/syrupy (syrupy)

v5.5.3

Compare Source

v5.5.2

Compare Source

v5.5.1

Compare Source

v5.5.0

Compare Source

v5.4.0

Compare Source

v5.3.4

Compare Source

v5.3.3

Compare Source

v5.3.2

Compare Source

v5.3.1

Compare Source

v5.3.0

Compare Source

v5.2.0

Compare Source

v5.1.0

Compare Source

Features
  • add serializer plugin system; plugins for data models (#​1062) (df9bc8f)

v5.0.0

Compare Source

Bug Fixes
  • Block terminal summary for xdist workers. (#​978) (33a848d)
  • ensure syrupy's pytest_assertrepr_compare hook is called first. (#​984) (eb0024d)
Code Refactoring
  • remove incorrect private underscore prefix from public methods (8cfc905)
Features
BREAKING CHANGES
  • The following methods have been renamed:

SnapshotCollectionStorage

  • _read_snapshot_collection -> read_snapshot_collection
  • _read_snapshot_data_from_location -> read_snapshot_data_from_location
  • _write_snapshot_collection -> write_snapshot_collection
  • _get_file_basename -> get_file_basename
  • _file_extension -> file_extension

AmberDataSerializer

  • _snapshot_sort_key -> snapshot_sort_key

Renamed constants to improve clarity:

constants

  • SNAPSHOT_EMPTY_FOSSIL_KEY -> SNAPSHOT_EMPTY_COLLECTION_KEY
  • SNAPSHOT_UNKNOWN_FOSSIL_KEY -> SNAPSHOT_UNKNOWN_COLLECTION_KEY
  • Min. python version is now 3.10.
  • The Syrupy project is switching from Apache 2.0 to a more permissive MIT license. By using Syrupy >=5, you agree to abide by this new license. You can continue to use Syrupy v1 through v4 under Apache 2.0.
  • Drops support for Python 3.8 which is end of life as of October 2024. Raises the minimum version of pytest to v8.

4.9.1 (2025-03-24)

Bug Fixes
  • serializer: preserve trailing newlines in ambr serialization (#​950) (5897490)
  • serializer: preserve trailing newlines in ambr serialization (#​950) (5037477)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Sep 29, 2025

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock
Updating dependencies
Resolving dependencies...


The current project's supported Python range (>=3.9.1,<4.0) is not compatible with some of the required packages Python requirement:
  - syrupy requires Python >=3.10, so it will not be installable for Python >=3.9.1,<3.10
  - syrupy requires Python >=3.10, so it will not be installable for Python >=3.9.1,<3.10
  - syrupy requires Python >=3.10, so it will not be installable for Python >=3.9.1,<3.10
  - syrupy requires Python >=3.10, so it will not be installable for Python >=3.9.1,<3.10
  - syrupy requires Python >=3.10, so it will not be installable for Python >=3.9.1,<3.10
  - syrupy requires Python >=3.10, so it will not be installable for Python >=3.9.1,<3.10
  - syrupy requires Python >=3.10, so it will not be installable for Python >=3.9.1,<3.10
  - syrupy requires Python >=3.10, so it will not be installable for Python >=3.9.1,<3.10
  - syrupy requires Python >=3.10, so it will not be installable for Python >=3.9.1,<3.10
  - syrupy requires Python >=3.10, so it will not be installable for Python >=3.9.1,<3.10
  - syrupy requires Python >=3.10, so it will not be installable for Python >=3.9.1,<3.10
  - syrupy requires Python >=3.10, so it will not be installable for Python >=3.9.1,<3.10
  - syrupy requires Python >=3.10, so it will not be installable for Python >=3.9.1,<3.10

Because no versions of syrupy match >5.0.0,<5.1.0 || >5.1.0,<5.2.0 || >5.2.0,<5.3.0 || >5.3.0,<5.3.1 || >5.3.1,<5.3.2 || >5.3.2,<5.3.3 || >5.3.3,<5.3.4 || >5.3.4,<5.4.0 || >5.4.0,<5.5.0 || >5.5.0,<5.5.1 || >5.5.1,<5.5.2 || >5.5.2,<5.5.3 || >5.5.3,<6.0.0
 and syrupy (5.0.0) requires Python >=3.10, syrupy is forbidden.
And because syrupy (5.1.0) requires Python >=3.10, syrupy is forbidden.
And because syrupy (5.2.0) requires Python >=3.10
 and syrupy (5.3.0) requires Python >=3.10, syrupy is forbidden.
And because syrupy (5.3.1) requires Python >=3.10
 and syrupy (5.3.2) requires Python >=3.10, syrupy is forbidden.
And because syrupy (5.3.3) requires Python >=3.10
 and syrupy (5.3.4) requires Python >=3.10, syrupy is forbidden.
And because syrupy (5.4.0) requires Python >=3.10
 and syrupy (5.5.0) requires Python >=3.10, syrupy is forbidden.
And because syrupy (5.5.1) requires Python >=3.10
 and syrupy (5.5.2) requires Python >=3.10, syrupy is forbidden.
So, because syrupy (5.5.3) requires Python >=3.10
 and nice-go depends on syrupy (^5.0.0), version solving failed.

  * Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties

    For syrupy, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For syrupy, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For syrupy, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For syrupy, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For syrupy, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For syrupy, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For syrupy, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For syrupy, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For syrupy, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For syrupy, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For syrupy, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For syrupy, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For syrupy, a possible solution would be to set the `python` property to ">=3.10,<4.0"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers


@renovate
renovate Bot force-pushed the renovate/syrupy-5.x branch 9 times, most recently from 00f4710 to 3c9ceb8 Compare October 7, 2025 01:35
@renovate
renovate Bot force-pushed the renovate/syrupy-5.x branch 12 times, most recently from da6219b to 86e5e4b Compare October 14, 2025 04:40
@renovate
renovate Bot force-pushed the renovate/syrupy-5.x branch 8 times, most recently from c14b906 to 04946b4 Compare October 17, 2025 06:05
@renovate
renovate Bot force-pushed the renovate/syrupy-5.x branch 10 times, most recently from ea62ba2 to 196d578 Compare October 30, 2025 12:10
@renovate
renovate Bot force-pushed the renovate/syrupy-5.x branch 19 times, most recently from bffd739 to a28b458 Compare June 19, 2026 14:58
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.

0 participants