Update @nuxtjs/plausible 0.2.1 → 0.2.4 (minor) #766
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @nuxtjs/plausible (0.2.1 → 0.2.4) · Repo
Release Notes
0.2.4
0.2.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 22 commits:
chore: release v0.2.4
ci: update action versions
chore: fix linting errors
chore: remove `prepare` from package scripts
chore: fix type issues
chore: upgrade dependencies
chore: use module-builder stub mode for more accurate types (#12)
chore: update README
docs: update og image
chore: release v0.2.3
ci: fix release pipeline
chore: release v0.2.2
fix: explicit composable imports
chore: upgrade dependencies
refactor: remove obsolete imports
refactor: use `createResolver` for relative paths
ci: add linting pipeline
chore: format with Prettier v3
fix: README options table (#8)
chore: upgrade dependencies
chore: upgrade dependencies
chore: upgrade to Nuxt 3.5.1
✳️ ufo (1.3.0 → 1.3.2) · Repo · Changelog
Release Notes
1.3.2
1.3.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 15 commits:
fix: respect fragment in trailing slash utils (#175)
chore: update lockfile
chore(deps): update actions/setup-node action to v4 (#182)
chore(deps): update all non-major dependencies (#187)
fix(parseURL): parse protocol case-insensitively (#188)
chore(deps): update all non-major dependencies
chore(deps): update autofix-ci/action digest to d3e5915
chore(deps): update all non-major dependencies
chore(release): v1.3.1
chore: update dependencies
fix: test script protocols insensitively (#180)
chore(deps): update all non-major dependencies
chore(deps): update all non-major dependencies
chore(deps): update all non-major dependencies
chore(release): v1.3.0
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.