Problem/Motivation

It looks like semver treats 0.0.x releases differently with the ^selector:

    - drupal/opentelemetry 1.0.0-beta5 requires open-telemetry/opentelemetry-propagation-traceresponse ^0.0.3 -> found open-telemetry/opentelemetry-propagation-traceresponse[0.0.3] but it conflicts with your root composer.json require (0.0.5).

https://github.com/opentelemetry-php/contrib-propagator-traceresponse/co... just shows the PHP 8.4 compatibility fix and nothing else that's functional, so I think that's safe to update. Didn't review 0.1.0 yet, that's for another day.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork opentelemetry-3570744

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

berdir created an issue. See original summary.

berdir opened merge request !75

  • berdir committed 80a9f9d2 on 1.0.x 
    feat: #3570744 Bump open-telemetry/opentelemetry-propagation-...
berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Title: Bump open-telemetry/opentelemetry-propagation-traceresponse dependency to 0.0.5 » Bump open-telemetry/opentelemetry-propagation-traceresponse dependency to 0.0.5 for PHP 8.4 compatibility
Status: Active » Fixed

Merged this, don't see there being any risk with this.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.