-
Notifications
You must be signed in to change notification settings - Fork 13.4k
chore(deps): update @stencil/vue-output-target to v0.11.8 #30609
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
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@brandyscarney
brandyscarney
changed the title
(削除) chore(deps): update @stencil/vue-output-target to v0.11.8 in vue (削除ここまで)
(追記) chore(deps): update @stencil/vue-output-target to v0.11.8 (追記ここまで)
Aug 7, 2025
...30585) This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [@stencil/vue-output-target](https://stenciljs.com/) ([source](https://redirect.github.com/stenciljs/output-targets)) | [`0.10.8` -> `0.11.8`](https://renovatebot.com/diffs/npm/@stencil%2fvue-output-target/0.10.8/0.11.8) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>stenciljs/output-targets (@​stencil/vue-output-target)</summary> ### [`v0.11.8`](https://redirect.github.com/stenciljs/output-targets/compare/@stencil/vue-output-target@0.10.8...32f98e2301193518a63f5d25c7e3f9e7384697e3) [Compare Source](https://redirect.github.com/stenciljs/output-targets/compare/@stencil/vue-output-target@0.10.8...32f98e2301193518a63f5d25c7e3f9e7384697e3) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "every weekday before 11am" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Never, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/ionic-team/ionic-framework). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS40My41IiwidXBkYXRlZEluVmVyIjoiNDEuNDYuMyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@brandyscarney
brandyscarney
force-pushed
the
chore/vue-output-target
branch
from
August 7, 2025 15:42
a22c0f4 to
43be95d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Uh oh!
There was an error while loading. Please reload this page.
Issue number: N/A
What is the current behavior?
Vue output target was updated in core but not in
vueorvue-routerWhat is the new behavior?
Run the build & update the dep in
vueandvue-routerDoes this introduce a breaking change?
Other information
At first I tried to update the
vue-routerpackage-lock version but I realized that it gets updated on release here: 4c1d012