https://github.com/breadadams/renovate-semantic-commit-repro

https://github.com/breadadams/renovate-semantic-commit-repro

Last synced: 24 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/breadadams/renovate-semantic-commit-repro
• Owner: breadadams
• Created: 2024-10-15T18:45:17.000Z (3 months ago)
• Default Branch: main
• Last Pushed: 2024-10-15T19:11:54.000Z (3 months ago)
• Last Synced: 2024-10-27T23:36:21.254Z (2 months ago)
• Size: 9.77 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 3
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# renovate-semantic-commit-repro

> This repo contains the repro for this discussion: https://github.com/renovatebot/renovate/discussions/31973

## What it contains

A basic monorepo setup using Yarn workspaces, containing two packages:

- `pkg-a`

- `pkg-b`

### `pkg-a`

Contains the following dependencies:

- `lodash`, under `dependencies`, one version behind the latest.

- `ramda`, under `devDependencies`, one version behind the latest.

### `pkg-b`

Contains the following dependencies (basically the inverse of `pkg-a`):

- `lodash`, under `devDependencies`, one version behind the latest.

- `ramda`, under `dependencies`, one version behind the latest.

## The problem

When Renovate opens PRs bumping `lodash` and `ramda`, it uses different commit prefixes:

- `lodash` gets the `chore` prefix because it is listed under `devDependencies` in `pkg-b`.

- `ramda` gets the `fix` prefix because it is listed under `dependencies.` in `pkg-b`.

I'd imagine both of the PRs should have the `fix` prefix, since both these dependencies are listed under `dependencies` for at least 1 of the packages within the monorepo.