mirror of
https://github.com/NdoleStudio/httpsms.git
synced 2026-04-26 11:25:49 +03:00
[PR #313] [MERGED] chore(deps-dev): bump @nuxt/typescript-build from 2.1.0 to 3.0.2 in /web #343
Labels
No labels
In Review
documentation
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/httpsms#343
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/NdoleStudio/httpsms/pull/313
Author: @dependabot[bot]
Created: 12/1/2023
Status: ✅ Merged
Merged: 12/11/2023
Merged by: @AchoArnold
Base:
main← Head:dependabot/npm_and_yarn/web/nuxt/typescript-build-3.0.2📝 Commits (1)
77e7c9cchore(deps-dev): bump @nuxt/typescript-build from 2.1.0 to 3.0.2 in /web📊 Changes
2 files changed (+16 additions, -19 deletions)
View changed files
📝
web/package.json(+1 -1)📝
web/pnpm-lock.yaml(+15 -18)📄 Description
Bumps @nuxt/typescript-build from 2.1.0 to 3.0.2.
Release notes
Sourced from
@nuxt/typescript-build's releases.Commits
056307dPublish8913e9ddocs: replacetypescript@4withtypescriptsince v5 is allowed too1e882dcdocs: be more specific about Nuxt version in readme8189014docs: fix case of reference to the typeCheck option108243fchore(deps): lock file maintenance (package.json) (#605)c81840bchore(deps): lock file maintenance (packages/typescript-runtime/package.json)...1ae43b4chore(deps): lock file maintenance (packages/typescript-build/package.json) (...b1123b2chore(deps): update devdependency lerna to v7 (#609)4ee9ae1chore(deps): update dependency ts-node to v10 (#510)0da0f56chore(deps): update all non-major dependencies (#620)Maintainer changes
This version was pushed to npm by rchl, a new releaser for
@nuxt/typescript-buildsince your current version.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.