Skip to content
This repository was archived by the owner on Mar 16, 2026. It is now read-only.

Update dependency patchlevel/event-sourcing to v3#26

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/patchlevel-event-sourcing-3.x
Open

Update dependency patchlevel/event-sourcing to v3#26
renovate[bot] wants to merge 1 commit intomainfrom
renovate/patchlevel-event-sourcing-3.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 16, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
patchlevel/event-sourcing (source) ^2.1.0 → ^2.1.0 || ^3.0.0 age adoption passing confidence

Release Notes

patchlevel/event-sourcing (patchlevel/event-sourcing)

v3.18.0

Compare Source

Release Notes for 3.18.0

Feature release (minor)

3.18.0
  • Total issues resolved: 0
  • Total pull requests resolved: 3
  • Total contributors: 1
enhancement

v3.17.0

Compare Source

Release Notes for 3.17.0

Feature release (minor)

3.17.0
  • Total issues resolved: 0
  • Total pull requests resolved: 3
  • Total contributors: 1
enhancement

v3.16.0

Compare Source

Release Notes for 3.16.0

Feature release (minor)

3.16.0
  • Total issues resolved: 0
  • Total pull requests resolved: 2
  • Total contributors: 1
enhancement
documentation

v3.15.0

Compare Source

Release Notes for 3.15.0

Feature release (minor)

3.15.0
  • Total issues resolved: 0
  • Total pull requests resolved: 4
  • Total contributors: 2
documentation
enhancement

v3.14.1

Compare Source

Release Notes for 3.14.1

3.14.x bugfix release (patch)

3.14.1
  • Total issues resolved: 0
  • Total pull requests resolved: 0
  • Total contributors: 0
Something was forgotten in release 3.14.0...

v3.14.0

Compare Source

Release Notes for 3.14.0

Feature release (minor)

3.14.0
  • Total issues resolved: 0
  • Total pull requests resolved: 1
  • Total contributors: 1
enhancement

v3.13.1

Compare Source

Release Notes for 3.13.1

3.13.x bugfix release (patch)

3.13.1
  • Total issues resolved: 0
  • Total pull requests resolved: 1
  • Total contributors: 1
bug

v3.13.0

Compare Source

Release Notes for 3.13.0

Feature release (minor)

3.13.0
  • Total issues resolved: 0
  • Total pull requests resolved: 2
  • Total contributors: 1
enhancement

v3.12.1

Compare Source

Release Notes for 3.12.1

3.12.x bugfix release (patch)

3.12.1

v3.12.0

Compare Source

Release Notes for 3.12.0

Feature release (minor)

3.12.0
  • Total issues resolved: 0
  • Total pull requests resolved: 7
  • Total contributors: 3
bug
documentation
enhancement

v3.11.0

Compare Source

Release Notes for 3.11.0

Feature release (minor)

3.11.0
  • Total issues resolved: 0
  • Total pull requests resolved: 11
  • Total contributors: 3
enhancement
dependencies
documentation

v3.10.4

Compare Source

Release Notes for 3.10.4

3.10.x bugfix release (patch)

3.10.4
  • Total issues resolved: 0
  • Total pull requests resolved: 3
  • Total contributors: 2
bug
documentation

v3.10.3

Compare Source

Release Notes for 3.10.3

3.10.x bugfix release (patch)

3.10.3
  • Total issues resolved: 0
  • Total pull requests resolved: 1
  • Total contributors: 1
bug

v3.10.2

Compare Source

Release Notes for 3.10.2

3.10.x bugfix release (patch)

3.10.2

nothing changed

v3.10.1

Compare Source

Release Notes for 3.10.1

3.10.x bugfix release (patch)

3.10.1
  • Total issues resolved: 0
  • Total pull requests resolved: 1
  • Total contributors: 1
BC-Break,bug

v3.10.0

Compare Source

Release Notes for 3.10.0

Feature release (minor)

3.10.0
  • Total issues resolved: 0
  • Total pull requests resolved: 4
  • Total contributors: 1
enhancement

v3.9.0

Compare Source

Release Notes for 3.9.0

Feature release (minor)

3.9.0
  • Total issues resolved: 0
  • Total pull requests resolved: 2
  • Total contributors: 1
enhancement

v3.8.1

Compare Source

Release Notes for 3.8.1

3.8.x bugfix release (patch)

3.8.1
  • Total issues resolved: 0
  • Total pull requests resolved: 1
  • Total contributors: 1
bug

v3.8.0

Compare Source

Release Notes for 3.8.0

Feature release (minor)

3.8.0
  • Total issues resolved: 0
  • Total pull requests resolved: 8
  • Total contributors: 1
bug
enhancement

v3.7.0

Compare Source

Release Notes for 3.7.0

Feature release (minor)

3.7.0
  • Total issues resolved: 0
  • Total pull requests resolved: 3
  • Total contributors: 1
enhancement

v3.6.3

Compare Source

Release Notes for 3.6.3

3.6.x bugfix release (patch)

3.6.3
  • Total issues resolved: 0
  • Total pull requests resolved: 1
  • Total contributors: 1
bug

v3.6.2

Compare Source

Release Notes for 3.6.2

3.6.x bugfix release (patch)

3.6.2
  • Total issues resolved: 0
  • Total pull requests resolved: 1
  • Total contributors: 1
bug

v3.6.1

Compare Source

What's Changed

Full Changelog: patchlevel/event-sourcing@3.6.0...3.6.1

v3.6.0

Compare Source

Release Notes for 3.6.0

Feature release (minor)

This release has changes that would be classified as BC breaks in our experimental components. Since these features are experimental, we can change the API or remove them completely even in a major release. See our documentation: https://event-sourcing.patchlevel.io/latest/our-backward-compatibility-promise/

The following has changed:

StreamDoctrineDbalStore:
A new required database field called event_id has been added and the fields event have been renamed event_name and payload have been renamed event_payload. Make sure to adjust the migration generation accordingly! In addition, the StreamHeader has been split into the following headers: StreamNameHeader, PlayheadHeader and RecordedOnHeader.

Tracing:
This feature has been completely removed.

3.6.0
  • Total issues resolved: 0
  • Total pull requests resolved: 6
  • Total contributors: 1
enhancement
BC-Break

v3.5.1

Compare Source

Release Notes for 3.5.1

3.5.x bugfix release (patch)

3.5.1
  • Total issues resolved: 0
  • Total pull requests resolved: 1
  • Total contributors: 1
bug

v3.5.0

Compare Source

Release Notes for 3.5.0

Feature release (minor)

3.5.0
  • Total issues resolved: 0
  • Total pull requests resolved: 4
  • Total contributors: 1
bug
enhancement

v3.4.0

Compare Source

Release Notes for 3.4.0

Feature release (minor)

3.4.0
  • Total issues resolved: 0
  • Total pull requests resolved: 7
  • Total contributors: 2
bug
enhancement
dependencies

v3.3.0

Compare Source

Release Notes for 3.3.0

Feature release (minor)

3.3.0
  • Total issues resolved: 0
  • Total pull requests resolved: 1
  • Total contributors: 1
enhancement

v3.2.0

Compare Source

Release Notes for 3.2.0

Feature release (minor)

3.2.0
  • Total issues resolved: 0
  • Total pull requests resolved: 1
  • Total contributors: 1
enhancement

v3.1.0

Compare Source

Release Notes for 3.1.0

Feature release (minor)

3.1.0
  • Total issues resolved: 0
  • Total pull requests resolved: 5
  • Total contributors: 3
enhancement

v3.0.0

Compare Source

Release Notes for 3.0.0

Upgrade path from 2.x to 3.0.0: https://patchlevel.github.io/event-sourcing-docs/latest/UPGRADE-3.0/
Migrate from MultiTableStore to SingleTableStore (pre-requirement): https://patchlevel.github.io/event-sourcing-docs/2.3/migrate-multi-table-store-to-single-table-store/

Backwards incompatible release (major)

3.0.0
  • Total issues resolved: 0
  • Total pull requests resolved: 137
BC-Break
bug
documentation
dependencies
enhancement
BC-Break,enhancement
bug,enhancement
BC-Break,bug
BC-Break,bug,enhancement

@renovate renovate bot added the renovate label Mar 16, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Mar 16, 2026

⚠️ 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: composer.lock
Command failed: composer update patchlevel/event-sourcing:3.18.0 --with-dependencies --ignore-platform-req=ext-* --ignore-platform-req=lib-* --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins --minimal-changes
Loading composer repositories with package information
Dependency doctrine/migrations is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency psr/container is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires patchlevel/event-sourcing ^2.1.0 || ^3.0.0 -> satisfiable by patchlevel/event-sourcing[3.18.0].
    - patchlevel/event-sourcing 3.18.0 requires doctrine/dbal ^4.0.0 -> found doctrine/dbal[4.0.0, ..., 4.4.2] but these were not loaded, likely because it conflicts with another require.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

@renovate
Update dependency patchlevel/event-sourcing to v3
0deba9b 
| datasource | package                   | from  | to     |
| ---------- | ------------------------- | ----- | ------ |
| packagist  | patchlevel/event-sourcing | 2.1.0 | 3.18.0 |


Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/patchlevel-event-sourcing-3.x branch from cb7489a to 0deba9b Compare March 16, 2026 08:40
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants