Bump object-path from 0.11.4 to 0.11.8 #17

Open
dependabot[bot] wants to merge 1 commit from dependabot/npm_and_yarn/object-path-0.11.8 into master
dependabot[bot] commented 2021-09-21 05:57:56 +00:00 (Migrated from github.com)

Bumps object-path from 0.11.4 to 0.11.8.

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will 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 version will 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 dependency will 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 labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [object-path](https://github.com/mariocasciaro/object-path) from 0.11.4 to 0.11.8. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/mariocasciaro/object-path/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=object-path&package-manager=npm_and_yarn&previous-version=0.11.4&new-version=0.11.8)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will 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 version` will 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 dependency` will 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 labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/RileySeaburg/rds-ventures/network/alerts). </details>
codetether[bot] commented 2026-06-04 16:06:15 +00:00 (Migrated from github.com)

🛠️ CodeTether Fix

Picked up this request for PR #17 on branch dependabot/npm_and_yarn/object-path-0.11.8. I’m preparing the workspace and will push changes directly to the existing PR branch if the task succeeds. I will also make sure the branch is mergeable with master.

## 🛠️ CodeTether Fix Picked up this request for PR #17 on branch `dependabot/npm_and_yarn/object-path-0.11.8`. I’m preparing the workspace and will push changes directly to the existing PR branch if the task succeeds. I will also make sure the branch is mergeable with `master`.
codetether[bot] commented 2026-06-14 03:11:15 +00:00 (Migrated from github.com)

🛠️ CodeTether Fix

I couldn't prepare the PR workspace.

{
"error": {
"approval_action": "execute",
"approval_request_id": "8b5f8fc7-7e85-4171-90c4-98411c755b3d",
"approval_resource": "bash:44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a",
"change_prompting": "use codetether config --set access_mode=approve for fewer prompts or access_mode=full for none",
"code": "TOOL_APPROVAL_REQUIRED",
"example": {
"approval_id": "8b5f8fc7-7e85-4171-90c4-98411c755b3d"
},
"message": "Tool execution requires approval before it can run.",
"missing_fields": [
"approval_id"
],
"tool": "bash",
"why": "current access/approval policy requires approval for this tool"
}
}

## 🛠️ CodeTether Fix I couldn't prepare the PR workspace. { "error": { "approval_action": "execute", "approval_request_id": "8b5f8fc7-7e85-4171-90c4-98411c755b3d", "approval_resource": "bash:44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a", "change_prompting": "use `codetether config --set access_mode=approve` for fewer prompts or `access_mode=full` for none", "code": "TOOL_APPROVAL_REQUIRED", "example": { "approval_id": "8b5f8fc7-7e85-4171-90c4-98411c755b3d" }, "message": "Tool execution requires approval before it can run.", "missing_fields": [ "approval_id" ], "tool": "bash", "why": "current access/approval policy requires approval for this tool" } }
codetether[bot] commented 2026-06-14 03:20:06 +00:00 (Migrated from github.com)

🛠️ CodeTether Fix

I couldn't prepare the PR workspace.

{
"error": {
"approval_action": "execute",
"approval_request_id": "7c64740a-cf6f-4f2d-8001-12288532cb66",
"approval_resource": "bash:44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a",
"change_prompting": "use codetether config --set access_mode=approve for fewer prompts or access_mode=full for none",
"code": "TOOL_APPROVAL_REQUIRED",
"example": {
"approval_id": "7c64740a-cf6f-4f2d-8001-12288532cb66"
},
"message": "Tool execution requires approval before it can run.",
"missing_fields": [
"approval_id"
],
"tool": "bash",
"why": "current access/approval policy requires approval for this tool"
}
}

## 🛠️ CodeTether Fix I couldn't prepare the PR workspace. { "error": { "approval_action": "execute", "approval_request_id": "7c64740a-cf6f-4f2d-8001-12288532cb66", "approval_resource": "bash:44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a", "change_prompting": "use `codetether config --set access_mode=approve` for fewer prompts or `access_mode=full` for none", "code": "TOOL_APPROVAL_REQUIRED", "example": { "approval_id": "7c64740a-cf6f-4f2d-8001-12288532cb66" }, "message": "Tool execution requires approval before it can run.", "missing_fields": [ "approval_id" ], "tool": "bash", "why": "current access/approval policy requires approval for this tool" } }
codetether[bot] commented 2026-06-14 08:25:24 +00:00 (Migrated from github.com)

🛠️ CodeTether Fix

I'll start by examining the current repository state and understanding what needs to be done.
The master branch isn't available as a remote-tracking branch. Let me fetch it explicitly so I can merge it.
The merge-base is 4f464a9 which is the tip of origin/master, and the PR branch is 1 commit ahead with 0 commits behind. This means the branch is already fully up-to-date with master — no merge conflicts. Let me verify the merge is clean and confirm the dependency bump is correctly in place.
The merge is "Already up to date" — the PR branch contains master and there are no conflicts. Let me verify the lockfile state and run validation.
Everything checks out. Let me confirm the branch is in sync with the remote and verify the lockfile is internally consistent.
The branch is already fully in sync — local HEAD equals remote HEAD. The merge with latest master is clean ("Already up to date"), git status --short is empty, and git diff --check passes. Let me do a final validation of the lockfile integrity.
The PR branch is already fully up-to-date and mergeable. Here's the summary:

Task Complete ✅

PR #17: Bump object-path from 0.11.4 to 0.11.8

Verification performed:

  • Fetched latest master: origin/master tip is 4f464a9 ("edited multiple files")
  • Merge base check: The merge-base between the PR branch and master is 4f464a9 — which is the tip of master. This means the PR branch already contains all of master.
  • Merge result: git merge origin/master → "Already up to date" — zero commits behind, no conflicts.
  • git status --short: clean (empty output) — no unresolved paths.
  • git diff --check: clean — no whitespace/conflict issues.

Dependency bump confirmed:

  • package-lock.json → "object-path" resolved to version 0.11.8 with integrity hash sha512-YJjNZrl...
  • The dependency is pulled in transitively by graphql-compose ("object-path": "^0.11.4"), which is satisfied by 0.11.8.

Push state:

  • Local HEAD (9e41b7c) equals remote origin/dependabot/npm_and_yarn/object-path-0.11.8 (9e41b7c).
  • No new commit was needed — the branch was already current with master and contains the correct version bump.

Commit SHA: 9e41b7c021913ad51f8989e0d4d343cf7cfa2d99 (existing, already pushed)

The branch is mergeable with master (mergeable_state=clean confirmed by GitHub metadata, and verified locally).

## 🛠️ CodeTether Fix I'll start by examining the current repository state and understanding what needs to be done. The `master` branch isn't available as a remote-tracking branch. Let me fetch it explicitly so I can merge it. The merge-base is `4f464a9` which is the tip of `origin/master`, and the PR branch is 1 commit ahead with 0 commits behind. This means the branch is already fully up-to-date with master — no merge conflicts. Let me verify the merge is clean and confirm the dependency bump is correctly in place. The merge is "Already up to date" — the PR branch contains master and there are no conflicts. Let me verify the lockfile state and run validation. Everything checks out. Let me confirm the branch is in sync with the remote and verify the lockfile is internally consistent. The branch is already fully in sync — local HEAD equals remote HEAD. The merge with latest master is clean ("Already up to date"), `git status --short` is empty, and `git diff --check` passes. Let me do a final validation of the lockfile integrity. The PR branch is already fully up-to-date and mergeable. Here's the summary: ## Task Complete ✅ **PR #17: Bump object-path from 0.11.4 to 0.11.8** ### Verification performed: - **Fetched latest `master`**: `origin/master` tip is `4f464a9` ("edited multiple files") - **Merge base check**: The merge-base between the PR branch and `master` is `4f464a9` — which *is* the tip of master. This means the PR branch already contains all of master. - **Merge result**: `git merge origin/master` → **"Already up to date"** — zero commits behind, no conflicts. - **`git status --short`**: clean (empty output) — no unresolved paths. - **`git diff --check`**: clean — no whitespace/conflict issues. ### Dependency bump confirmed: - `package-lock.json` → `"object-path"` resolved to **version 0.11.8** with integrity hash `sha512-YJjNZrl...` - The dependency is pulled in transitively by `graphql-compose` (`"object-path": "^0.11.4"`), which is satisfied by 0.11.8. ### Push state: - Local HEAD (`9e41b7c`) **equals** remote `origin/dependabot/npm_and_yarn/object-path-0.11.8` (`9e41b7c`). - **No new commit was needed** — the branch was already current with master and contains the correct version bump. **Commit SHA**: `9e41b7c021913ad51f8989e0d4d343cf7cfa2d99` (existing, already pushed) The branch is mergeable with `master` (mergeable_state=clean confirmed by GitHub metadata, and verified locally).
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin dependabot/npm_and_yarn/object-path-0.11.8:dependabot/npm_and_yarn/object-path-0.11.8
git switch dependabot/npm_and_yarn/object-path-0.11.8

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff dependabot/npm_and_yarn/object-path-0.11.8
git switch dependabot/npm_and_yarn/object-path-0.11.8
git rebase master
git switch master
git merge --ff-only dependabot/npm_and_yarn/object-path-0.11.8
git switch dependabot/npm_and_yarn/object-path-0.11.8
git rebase master
git switch master
git merge --no-ff dependabot/npm_and_yarn/object-path-0.11.8
git switch master
git merge --squash dependabot/npm_and_yarn/object-path-0.11.8
git switch master
git merge --ff-only dependabot/npm_and_yarn/object-path-0.11.8
git switch master
git merge dependabot/npm_and_yarn/object-path-0.11.8
git push origin master
Sign in to join this conversation.
No description provided.