Skip to content
This repository has been archived by the owner on Dec 12, 2020. It is now read-only.

[Question] Release notes for a group #403

Closed
sjparkinson opened this issue Oct 30, 2019 · 2 comments
Closed

[Question] Release notes for a group #403

sjparkinson opened this issue Oct 30, 2019 · 2 comments
Assignees

Comments

@sjparkinson
Copy link

Which Renovate are you using? CLI, App, or Pro

GitHub App

Which platform are you using? GitHub, GitLab, Bitbucket Azure DevOps

GitHub

Have you checked the logs? Don't forget to include them if relevant

https://app.renovatebot.com/dashboard#github/Financial-Times/next-epaper/107904904

What is your question?

We have defined a group for a monorepo that we publish as individual packages.

    {
      "packagePatterns": [
        "^@financial-times/dotcom-"
      ],
      "rangeStrategy": "auto",
      "masterIssueApproval": false,
      "groupName": "page kit monorepo",
      "groupSlug": "page-kit"
    }

https://github.com/Financial-Times/renovate-config-next/blob/master/renovate.json#L91-L99

The PR's opened (e.g. on Financial-Times/next-epaper) don't include any release notes.

The release notes are published in the GitHub release on the Financial-Times/dotcom-page-kit repository (which is private for now).

Is there anything we can do to get the release notes appearing on the Renovate PRs?

@rarkins
Copy link
Collaborator

rarkins commented Oct 30, 2019

Looks like it could potentially be the same issue as renovatebot/renovate#4724

Can you read through it’s discussion and see? Eg do you have nested changelog files?

@stale
Copy link

stale bot commented Nov 2, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon if no further activity occurs.

@stale stale bot added the wontfix label Nov 2, 2019
@stale stale bot closed this as completed Nov 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants