Loosening the primer/primitives dependency to any minor.patch version

[jonrohan]

I had tightened this dependency back up recently but we lost the ability to update primitives in dotcom and skip the update here. So I'm bringing back the ^ which will use any ^ version greater than what's in package.json as long as it's not a major release.

/cc @primer/css-reviewers

[changeset-bot]

🦋 Changeset detected

Latest commit: d0432d1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@primer/css	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[simurai]

Does that mean we have to be more careful what is considered major and minor/patch on primer/primitives? Having the ^ in the VS Code theme caused that red color bug: primer/github-vscode-theme#210.

[jonrohan]

Does that mean we have to be more careful what is considered major and minor/patch on primer/primitives? Having the ^ in the VS Code theme caused that red color bug: primer/github-vscode-theme#210.

that is true, but we do have the advantage of dotcom not being auto updated like the vscode theme.