ambimax/semantic-release-composer

@ambimax/semantic-release-composer

semantic-release plugin to update a composer package for php.

Step	Description
verifyConditions	Verify the presence of a composer.json file.
prepare	Update the composer.json version

Install

$ npm install @ambimax/semantic-release-composer -D

Usage

The plugin can be configured in the semantic-release configuration file:

{
  "tagFormat": "${version}",
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    "@ambimax/semantic-release-composer"
  ]
}

Configuration

Options

Options	Description	Default
skipOnMissingComposerJson	Silently ignore missing composer.json file	false

Examples

{
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    "@semantic-release/github",
    [
      "@semantic-release/changelog",
      {
        "changelogFile": "CHANGELOG.md"
      }
    ],
    [
      "@ambimax/semantic-release-composer",
      {
        "skipOnMissingComposerJson": true
      }
    ],
    [
      "@semantic-release/git",
      {
        "assets": ["composer.json", "CHANGELOG.md"],
        "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
      }
    ]
  ]
}

Author

• Tobias Schifftner

semantic-release-composer's Issues

npm ERR! 404 Not Found - cant install plugin

Hi,

This plugin could be useful for my project, unfortunately im getting:

npm ERR! 404 Not Found - GET https://registry.npmjs.org/@ambimax%2fsemantic-release-composer - Not found
npm ERR! 404
npm ERR! 404  '@ambimax/semantic-release-composer@*' is not in the npm registry.

Is there a config error in the repo or Is this plug-in not publicly available?

Cheers,
Jamie

No release to Gitlab package registry

Using v1.0.0

When used alongside @semantic-release/gitlab in a GitLab project only the release is created while no artifact is generated in the package registry.

Gitlab docs on installing a Composer package states that "A package in the Package Registry" is required.

Is it a bug o it has not been meant to work on Gitlab?

[Question] There is an demo app?

I wonder if there is a PHP demo app using this plugin.

composer lock file warning after semantic release

I am using this plugin in a CI/CD pipeline that tags a version. Everything works fine. Once the version is tagged, we run additional workflows off of the tagged version (tests etc).

There is a warning message displayed when running off of the tagged version.

Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run `composer update` or `composer update <package name>`.

Apparently running the command composer update --lock before committing the changes generated during the release process after the new version number is set could resolve this issue.

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀