Skip to content

Missing component field in config schema - python monorepo #2573

@Carter-Apas

Description

@Carter-Apas

Hello, don't know if this is an error on my part but I have a monorepo with a Python package. I don't have a setup.py or a setup.cfg just a pyproject.toml. I notice it doesn't seem to pull the component name into PR titles:
chore(component-name): v1.0.0. I fixed it by adding the component in the config. The Node packages seem to pull directly from the package.json. Wondering if this is intended? I noticed component isn't in the schema too, happy to open a pr for this if unintentionally left out. Thanks :)

Environment details

  • OS:
  • Node.js version: v22.14.0
  • npm version: 11.4.2
  • release-please version: v4

Steps to reproduce

Create a release-please-config.json in a monorepo like this:

{
  "packages": {
    "lorem": {
      "path": "lorem",
      "release-type": "python"
    }
  }
}

Run release-please manifest-pr or release-please github-release.

Observe that the generated pull request has a generic title like:

chore: release 1.2.3
Add "component": "lorem" manually to the config:

{
  "packages": {
    "lorem": {
      "path": "lorem",
      "release-type": "python",
      "component": "lorem"
    }
  }
}

Delete previous pr and run the action again and the pull request title should be:

chore(lorem): release 1.2.3


Metadata

Metadata

Assignees

Labels

priority: p3Desirable enhancement or fix. May not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions