microsoft / microsoft/fluentui
fluent v8/v9 releases are not published to github releases
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 20.3k
- Forks
- 2.9k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 46
Description
Describe the issue:
Our partners are experimenting renovate in other repos to bump dependencies, which heavility relies on Github Releases to be able to provide changelog of new version that was released.
We stopped creating github releases around Sept 30, 2021 (I dont know why - reasoning TBA), thus renovate bot is not providing those.
🚨 Example PR with missing "changelog" in PR description:
https://github.com/microsoft/cloudpack/pull/244

✅ Example of PR with "changelog":
https://github.com/microsoft/cloudpack/pull/234

Direct partner feedback:
Without having those release notes, they have hard time judging the fluent bump - what is changing? What should they test? how can they review the changes?
It would be great to have the change notes always in the renovate PRs.
Actual behavior:
No Github Releases
Expected behavior:
Github releases work with synced changelog
Workaround
Thankfully, one can click on the actual change and see changelog generated with our release
-
click on the new version

-
changelog

Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the GitHub Releases history for Fluent UI around September 30, 2021, then trace the repository's release process that should publish v8 and v9 releases. Confirm how Renovate consumes those releases and verify that completed releases include synchronized changelogs and appear in Renovate PR descriptions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100