fix(pretext-native): replace workspace:^ dependency with semver range

[mandrade2]

⚠️ This PR was authored with assistance from an AI agent.

Problem

pretext-native@0.0.2 publishes with a workspace:^ dependency:

"dependencies": {
"@hexdrinker/pretext-native-core": "workspace:^"
}

npm view pretext-native@0.0.2 dependencies confirms the published manifest still contains workspace:^. The release workflow runs npm publish, which does not rewrite the Yarn workspace: protocol to a version range (only yarn npm publish does). As a result npm/Yarn consumers cannot resolve @hexdrinker/pretext-native-core and are forced to patch around it with resolutions:

"resolutions": {
"@hexdrinker/pretext-native-core": "0.0.2"
}

Fix

Use a concrete semver range. Local workspace linking is unaffected (core is a workspace member at 0.0.2, so ^0.0.2 still resolves to the workspace), and the published manifest becomes valid.

Note

This requires a republish (e.g. pretext-native@0.0.3) to take effect for npm consumers. Alternatively, the release workflow could be switched to yarn npm publish, which rewrites workspace: protocols automatically.

[mandrade2]

⚠️ This PR was authored with assistance from an AI agent.

Problem

pretext-native@0.0.2 publishes with a workspace:^ dependency:

"dependencies": {
"@hexdrinker/pretext-native-core": "workspace:^"
}

npm view pretext-native@0.0.2 dependencies confirms the published manifest still contains workspace:^. The release workflow runs npm publish, which does not rewrite the Yarn workspace: protocol to a version range (only yarn npm publish does). As a result npm/Yarn consumers cannot resolve @hexdrinker/pretext-native-core and are forced to patch around it with resolutions:

"resolutions": {
"@hexdrinker/pretext-native-core": "0.0.2"
}

Fix

Use a concrete semver range. Local workspace linking is unaffected (core is a workspace member at 0.0.2, so ^0.0.2 still resolves to the workspace), and the published manifest becomes valid.

Note

This requires a republish (e.g. pretext-native@0.0.3) to take effect for npm consumers. Alternatively, the release workflow could be switched to yarn npm publish, which rewrites workspace: protocols automatically.

[mandrade2]

⚠️ This PR was authored with assistance from an AI agent.

Problem

pretext-native@0.0.2 publishes with a workspace:^ dependency:

"dependencies": {
"@hexdrinker/pretext-native-core": "workspace:^"
}

npm view pretext-native@0.0.2 dependencies confirms the published manifest still contains workspace:^. The release workflow runs npm publish, which does not rewrite the Yarn workspace: protocol to a version range (only yarn npm publish does). As a result npm/Yarn consumers cannot resolve @hexdrinker/pretext-native-core and are forced to patch around it with resolutions:

"resolutions": {
"@hexdrinker/pretext-native-core": "0.0.2"
}

Fix

Use a concrete semver range. Local workspace linking is unaffected (core is a workspace member at 0.0.2, so ^0.0.2 still resolves to the workspace), and the published manifest becomes valid.

Note

This requires a republish (e.g. pretext-native@0.0.3) to take effect for npm consumers. Alternatively, the release workflow could be switched to yarn npm publish, which rewrites workspace: protocols automatically.

[mandrade2]

⚠️ This PR was authored with assistance from an AI agent.

Problem

pretext-native@0.0.2 publishes with a workspace:^ dependency:

"dependencies": {
"@hexdrinker/pretext-native-core": "workspace:^"
}

npm view pretext-native@0.0.2 dependencies confirms the published manifest still contains workspace:^. The release workflow runs npm publish, which does not rewrite the Yarn workspace: protocol to a version range (only yarn npm publish does). As a result npm/Yarn consumers cannot resolve @hexdrinker/pretext-native-core and are forced to patch around it with resolutions:

"resolutions": {
"@hexdrinker/pretext-native-core": "0.0.2"
}

Fix

Use a concrete semver range. Local workspace linking is unaffected (core is a workspace member at 0.0.2, so ^0.0.2 still resolves to the workspace), and the published manifest becomes valid.

Note

This requires a republish (e.g. pretext-native@0.0.3) to take effect for npm consumers. Alternatively, the release workflow could be switched to yarn npm publish, which rewrites workspace: protocols automatically.

[mandrade2]

⚠️ This PR was authored with assistance from an AI agent.

Problem

pretext-native@0.0.2 publishes with a workspace:^ dependency:

"dependencies": {
"@hexdrinker/pretext-native-core": "workspace:^"
}

npm view pretext-native@0.0.2 dependencies confirms the published manifest still contains workspace:^. The release workflow runs npm publish, which does not rewrite the Yarn workspace: protocol to a version range (only yarn npm publish does). As a result npm/Yarn consumers cannot resolve @hexdrinker/pretext-native-core and are forced to patch around it with resolutions:

"resolutions": {
"@hexdrinker/pretext-native-core": "0.0.2"
}

Fix

Use a concrete semver range. Local workspace linking is unaffected (core is a workspace member at 0.0.2, so ^0.0.2 still resolves to the workspace), and the published manifest becomes valid.

Note

This requires a republish (e.g. pretext-native@0.0.3) to take effect for npm consumers. Alternatively, the release workflow could be switched to yarn npm publish, which rewrites workspace: protocols automatically.

[mandrade2]

⚠️ This PR was authored with assistance from an AI agent.

Problem

pretext-native@0.0.2 publishes with a workspace:^ dependency:

"dependencies": {
"@hexdrinker/pretext-native-core": "workspace:^"
}

npm view pretext-native@0.0.2 dependencies confirms the published manifest still contains workspace:^. The release workflow runs npm publish, which does not rewrite the Yarn workspace: protocol to a version range (only yarn npm publish does). As a result npm/Yarn consumers cannot resolve @hexdrinker/pretext-native-core and are forced to patch around it with resolutions:

"resolutions": {
"@hexdrinker/pretext-native-core": "0.0.2"
}

Fix

Use a concrete semver range. Local workspace linking is unaffected (core is a workspace member at 0.0.2, so ^0.0.2 still resolves to the workspace), and the published manifest becomes valid.

Note

This requires a republish (e.g. pretext-native@0.0.3) to take effect for npm consumers. Alternatively, the release workflow could be switched to yarn npm publish, which rewrites workspace: protocols automatically.

[mandrade2]

⚠️ This PR was authored with assistance from an AI agent.

Problem

pretext-native@0.0.2 publishes with a workspace:^ dependency:

"dependencies": {
"@hexdrinker/pretext-native-core": "workspace:^"
}

npm view pretext-native@0.0.2 dependencies confirms the published manifest still contains workspace:^. The release workflow runs npm publish, which does not rewrite the Yarn workspace: protocol to a version range (only yarn npm publish does). As a result npm/Yarn consumers cannot resolve @hexdrinker/pretext-native-core and are forced to patch around it with resolutions:

"resolutions": {
"@hexdrinker/pretext-native-core": "0.0.2"
}

Fix

Use a concrete semver range. Local workspace linking is unaffected (core is a workspace member at 0.0.2, so ^0.0.2 still resolves to the workspace), and the published manifest becomes valid.

Note

This requires a republish (e.g. pretext-native@0.0.3) to take effect for npm consumers. Alternatively, the release workflow could be switched to yarn npm publish, which rewrites workspace: protocols automatically.

[mandrade2]

⚠️ This PR was authored with assistance from an AI agent.

Problem

pretext-native@0.0.2 publishes with a workspace:^ dependency:

"dependencies": {
"@hexdrinker/pretext-native-core": "workspace:^"
}

npm view pretext-native@0.0.2 dependencies confirms the published manifest still contains workspace:^. The release workflow runs npm publish, which does not rewrite the Yarn workspace: protocol to a version range (only yarn npm publish does). As a result npm/Yarn consumers cannot resolve @hexdrinker/pretext-native-core and are forced to patch around it with resolutions:

"resolutions": {
"@hexdrinker/pretext-native-core": "0.0.2"
}

Fix

Use a concrete semver range. Local workspace linking is unaffected (core is a workspace member at 0.0.2, so ^0.0.2 still resolves to the workspace), and the published manifest becomes valid.

Note

This requires a republish (e.g. pretext-native@0.0.3) to take effect for npm consumers. Alternatively, the release workflow could be switched to yarn npm publish, which rewrites workspace: protocols automatically.