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

chore: use composite action to resolve exact npm package version #251

Merged
merged 2 commits into from
Mar 8, 2024

Conversation

byCedric
Copy link
Member

@byCedric byCedric commented Mar 8, 2024

Linked issue

This removes a warning from GHA and helps clean up the workflows.

@byCedric byCedric merged commit 2d0efa6 into main Mar 8, 2024
15 checks passed
@byCedric byCedric deleted the ci/semver-check branch March 8, 2024 14:57
expo-bot pushed a commit that referenced this pull request Mar 8, 2024
## [1.4.0](1.3.0...1.4.0) (2024-03-08)

### New features

* use `vscode.workspace.fs` API to load Expo projects ([#252](#252)) ([5a596d1](5a596d1))

### Code changes

* add tests and replace minimatch with picomatch ([#248](#248)) ([519d179](519d179))

### Other chores

* bump all workflow actions to latest versions ([#250](#250)) ([5a4bf25](5a4bf25))
* bump minimal required vscode version ([#249](#249)) ([6c789b8](6c789b8))
* enable tests for vscode insiders versions ([#253](#253)) ([036af2b](036af2b))
* use composite action to resolve exact npm package version ([#251](#251)) ([2d0efa6](2d0efa6))
@expo-bot
Copy link
Contributor

expo-bot commented Mar 8, 2024

🎉 This PR is included in version 1.4.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

None yet

2 participants