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

Support 'workspace:^' notation in dependency versions #125

Merged
merged 3 commits into from
Dec 15, 2023

Conversation

cryptodev-2s
Copy link
Contributor

@cryptodev-2s cryptodev-2s commented Dec 15, 2023

Overview

This pull request addresses the issue where the 'workspace:^' notation was not being recognized as a valid specifier for dependency/peerDependencies versions in our package.json files.

Changes Made

  • Modified isValidPackageManifestVersionField to recognize workspace:^ as a valid version.

@cryptodev-2s cryptodev-2s requested a review from a team as a code owner December 15, 2023 20:30
@cryptodev-2s cryptodev-2s changed the title Support 'workspace:^' Notation in Dependency Versions Support 'workspace:^' notation in dependency versions Dec 15, 2023
@cryptodev-2s cryptodev-2s requested a review from mcmire December 15, 2023 21:04
Copy link
Contributor

@mcmire mcmire left a comment

Choose a reason for hiding this comment

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

I tested this out on snaps and this bug goes away. There is another bug that prevents create-release-branch from running, but that's because this tool doesn't support private packages yet. That's a separate issue and I'll make a ticket for it. Anyway, this looks good on its own though!

@cryptodev-2s cryptodev-2s merged commit b12e72e into main Dec 15, 2023
@cryptodev-2s cryptodev-2s deleted the fix/workspace-dependency-support branch December 15, 2023 22:43
@mcmire
Copy link
Contributor

mcmire commented Dec 15, 2023

Follow up to this — it seems there were some empty directories in packages/ and that caused the tool to throw an error. I've logged a ticket about this here: #128. But it doesn't seem like this deters the Snaps team from using this tool, it's just a minor inconvenience. So we can release a new version with this bugfix.

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.

2 participants