Skip to content

Force dev version dependencies to use dev version as well #7286

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

Closed
wants to merge 5 commits into from

Conversation

timotheeguerin
Copy link
Member

No description provided.

Copy link
Contributor

github-actions bot commented May 8, 2025

All changed packages have been documented.

  • @typespec/internal-build-utils
Show changes

@typespec/http - internal ✏️

Testing new dev range

@typespec/streams - internal ✏️

Testing new dev range

@typespec/compiler - internal ✏️

Testing new dev range

@typespec/openapi3 - internal ✏️

Testing new dev range

@typespec/openapi - internal ✏️

Testing new dev range

@typespec/http-server-js - internal ✏️

Testing new dev range

@typespec/internal-build-utils - fix ✏️

Prerelease only allows other prerelease

@azure-sdk
Copy link
Collaborator

azure-sdk commented May 8, 2025

You can try these changes here

🛝 Playground 🌐 Website 🛝 VSCode Extension

@timotheeguerin timotheeguerin changed the title Try force dev Force dev version dependencies to use dev version as well May 9, 2025
Copy link
Member

@chrisradek chrisradek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this makes sense given we always release dev versions immediately after publishing a new stable release.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Im actually going back on this a little bit. it is quite a pain to require this and using overrides does solve all the problems with using dev versions. You override that version you want to test and you only need to do that.
So have to make sure that this would be compatible with it.

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

Successfully merging this pull request may close these issues.

3 participants