Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Explain supported platforms for release note fetching #14971

Closed
HonkingGoose opened this issue Apr 5, 2022 · 2 comments · Fixed by #14972
Closed

Explain supported platforms for release note fetching #14971

HonkingGoose opened this issue Apr 5, 2022 · 2 comments · Fixed by #14972
Assignees
@HonkingGoose
Labels
core:changelogs Related to changelogs/release notes fetching priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:docs Documentation

Comments

@HonkingGoose
Copy link
Collaborator

Describe the proposed change(s).

A user recently asked about fetching release notes when using the Bitbucket Cloud platform and I could not find out from reading our docs. Turns out we do not have a Bitbucket datasource that can fetch the release notes, see issue #14964 and #14138 for more on that.

Our docs should explain on which platforms we support fetching release notes.

Maybe we can list the supported platforms in the fetchReleaseNotes config option section?
@HonkingGoose HonkingGoose added type:docs Documentation status:requirements Full requirements are not yet known, so implementation should not be started priority-5-triage core:changelogs Related to changelogs/release notes fetching labels Apr 5, 2022
@HonkingGoose HonkingGoose mentioned this issue Apr 5, 2022
Closed
@viceice
Copy link
Member

viceice commented Apr 5, 2022

sounds good to me

@HonkingGoose HonkingGoose added priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:in-progress and removed status:requirements Full requirements are not yet known, so implementation should not be started priority-5-triage labels Apr 5, 2022
@HonkingGoose HonkingGoose self-assigned this Apr 5, 2022
@HonkingGoose HonkingGoose mentioned this issue Apr 5, 2022
Merged
6 tasks
@renovate-release
Copy link
Collaborator

🎉 This issue has been resolved in version 32.19.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@HonkingGoose HonkingGoose

Labels
core:changelogs Related to changelogs/release notes fetching priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:docs Documentation
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

docs(fetchReleaseNotes): explain platform support, link to overview issue HonkingGoose/renovate
3 participants
@viceice @HonkingGoose @renovate-release