mirror of
https://github.com/mageddo/dns-proxy-server.git
synced 2026-04-25 09:25:56 +03:00
[PR #262] [CLOSED] Bump json-schema and jsprim in /app #371
Labels
No labels
bug
confirmed
discussion
duplicate
enhancement
feature
feature-request
not-planned
pull-request
secondary-feature
stale
triage
waiting-feedback
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/dns-proxy-server-mageddo#371
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/mageddo/dns-proxy-server/pull/262
Author: @dependabot[bot]
Created: 1/29/2023
Status: ❌ Closed
Base:
master← Head:dependabot/npm_and_yarn/app/json-schema-and-jsprim-0.4.0📝 Commits (1)
c9d87a8Bump json-schema and jsprim in /app📊 Changes
1 file changed (+71 additions, -31 deletions)
View changed files
📝
app/package-lock.json(+71 -31)📄 Description
Bumps json-schema and jsprim. These dependencies needed to be updated together.
Updates
json-schemafrom 0.2.3 to 0.4.0Commits
f6f6a3bUse a little more robust method of checking instancesef60987Update versionb62f1daProtect against constructor modification, #84fb427cdLink to json-schema-org repository in addition to site, fixes #5422f1461Don't allow proto property to be used for schema default/coerce, fixes #84c52a27cGet basic test to passb3f42b3Add security policy3b0cec3Update versionc28470fUpdate readme to acknowledge the state of the package7dff9cdMerge pull request #81 from hodovani/patch-1Updates
jsprimfrom 1.4.1 to 1.4.2Changelog
Sourced from jsprim's changelog.
Commits
5c8475fjoyent/node-jsprim#35 Backport json-schema 0.4.0 to version 1.4.xMaintainer changes
This version was pushed to npm by bahamat, a new releaser for jsprim since 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 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)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and languageYou can disable automated security fix PRs for this repo from the Security Alerts page.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.