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.

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

Release Notes are wrong #2901

Closed
thomhurst opened this issue May 22, 2024 · 8 comments
Closed

Release Notes are wrong #2901

thomhurst opened this issue May 22, 2024 · 8 comments

Comments

@thomhurst
Copy link
Contributor

Heya, because I'm using the new Microsoft.Testing.Platform packages, I'm getting dependabot updates for them.

However it's pulling through ancient release notes from 2018. I assume because you've got v1 tags that relate to an old version of MSTest?

SmartSelect_20240522_150011_Gmail

@Evangelink
Copy link
Member

Hi @thomhurst,

I have no idea how dependabot is generating the release notes but clearly something is off. We do ship the new platfrom from a private mirror repo and not from here.

@thomhurst
Copy link
Contributor Author

On nuget.org the project site link links to this repository. Maybe it's due to that.

@Evangelink
Copy link
Member

I can confirm this is working by looking at this metadata. I'll discuss with the team if we can point the private repo or how to workaround this.

@Evangelink
Copy link
Member

@thomhurst I will close this issue as it should now be fixed since we have open-sourced the extra component here, the link and notes will be accurate.

@thomhurst
Copy link
Contributor Author

Does commenting reopen this? I'd like to reopen because they seem to be a hybrid of different projects ATM. There are release notes that are relevent to testing platform. Then there's release notes that seem specific to MSTest.

Uploading Screenshot_20240717_161149_Gmail.jpg…

@Evangelink
Copy link
Member

AFAIK there is no way for us to fix this, this repo hosts multiple products with different release notes and it seems dependabot only looks at the release tab of the repo (which is not made to support multiple projects).

@thomhurst
Copy link
Contributor Author

I haven't actually looked into it but does the dotnet runtime repository have the same problem? They have all the extensions packages don't they, so would probably have the same problems. But if you can't fix no worries, just wanted to make you guys aware

@Evangelink
Copy link
Member

I'll sync with them but AFAIK they only have one version number for all their components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants