Bump object-path from 0.11.4 to 0.11.8 #27

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 04:49:14 +00:00

(Migrated from github.com)

Bumps object-path from 0.11.4 to 0.11.8.

Commits

See full diff in compare view

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/gatsbyblog/network/alerts). </details>

codetether[bot] commented

2026-06-04 16:02:49 +00:00

(Migrated from github.com)

🛠️ CodeTether Fix

Picked up this request for PR #27 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 #27 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 04:50:16 +00:00

(Migrated from github.com)

🛠️ CodeTether Fix

I'll handle this Dependabot PR for bumping object-path. Let me start by checking the current repository state and fetching the latest master.
Let me check the current state of the dependency and the package files.
The remote origin/master ref doesn't exist as expected. Let me check the actual remote refs.
The master ref wasn't fetched properly. Let me fetch all refs explicitly.
Interesting - the remote only has the dependabot branch. Let me check if master is the default branch under a different name.
Master exists at 6a0f740. Let me fetch it and examine the current state of the object-path dependency.
Master is at 6a0f740, which is the parent of the PR branch. Let me verify the divergence and find where object-path is referenced.
The PR branch is exactly 1 commit ahead of master with 0 commits behind — so there's a fast-forward relationship, no merge conflict. The grep for object-path returned nothing, which is odd. Let me look more broadly at where it might be defined (it could be a transitive dependency with a different key).
There's a yarn.lock file (not package-lock.json). Let me check both package.json and yarn.lock for object-path.
The PR has already updated yarn.lock to point object-path at 0.11.8. Let me verify the exact state of the bump commit and confirm it's complete and correct.
The PR branch is a clean fast-forward from master (0 behind, 1 ahead) — no merge conflicts. The Dependabot commit already correctly bumps object-path. Let me verify the object-path lock entry is correct and confirm mergeability by doing a test merge.
The lock file correctly resolves object-path to 0.11.8, and there are no conflicts. Let me do a final verification that the working tree is clean and the branch is already pushed (it's a fast-forward so master is behind our branch — the PR is already mergeable).
The working tree is clean with no whitespace issues. Let me confirm the remote branch is in sync and verify the final state.
The task is complete. Here's the summary:

Result: PR already mergeable — no changes needed

Branch: dependabot/npm_and_yarn/object-path-0.11.8
Commit SHA: c4fc63da24129280df3423be24bee7ac19650921

Verification performed

Check	Result
Fetch latest `master`	✅ `master` at `6a0f740` (the parent commit of the PR branch)
Merge conflict check	✅ No conflicts — the PR branch is a clean fast-forward (0 commits behind, 1 commit ahead)
`object-path` version in `yarn.lock`	✅ Correctly resolves to `0.11.8` with proper integrity hash
`git status --short`	✅ Clean working tree (no unresolved paths)
`git diff --check`	✅ No whitespace/conflict-marker issues
Local vs. remote sync	✅ Both at `c4fc63d` — already pushed

Why no edits were required

The Dependabot commit already correctly bumps the indirect dependency object-path from 0.11.4 to 0.11.8 in yarn.lock. Since master is the direct ancestor of this branch, the merge is a trivial fast-forward — there were no conflicts to resolve and no additional changes to make. The PR is mergeable with master as-is.

## 🛠️ CodeTether Fix I'll handle this Dependabot PR for bumping object-path. Let me start by checking the current repository state and fetching the latest master. Let me check the current state of the dependency and the package files. The remote `origin/master` ref doesn't exist as expected. Let me check the actual remote refs. The master ref wasn't fetched properly. Let me fetch all refs explicitly. Interesting - the remote only has the dependabot branch. Let me check if master is the default branch under a different name. Master exists at `6a0f740`. Let me fetch it and examine the current state of the object-path dependency. Master is at `6a0f740`, which is the parent of the PR branch. Let me verify the divergence and find where object-path is referenced. The PR branch is exactly 1 commit ahead of master with 0 commits behind — so there's a fast-forward relationship, **no merge conflict**. The `grep` for object-path returned nothing, which is odd. Let me look more broadly at where it might be defined (it could be a transitive dependency with a different key). There's a `yarn.lock` file (not `package-lock.json`). Let me check both `package.json` and `yarn.lock` for object-path. The PR has already updated `yarn.lock` to point object-path at 0.11.8. Let me verify the exact state of the bump commit and confirm it's complete and correct. The PR branch is a clean fast-forward from master (0 behind, 1 ahead) — no merge conflicts. The Dependabot commit already correctly bumps object-path. Let me verify the object-path lock entry is correct and confirm mergeability by doing a test merge. The lock file correctly resolves object-path to 0.11.8, and there are no conflicts. Let me do a final verification that the working tree is clean and the branch is already pushed (it's a fast-forward so master is behind our branch — the PR is already mergeable). The working tree is clean with no whitespace issues. Let me confirm the remote branch is in sync and verify the final state. The task is complete. Here's the summary: ## Result: PR already mergeable — no changes needed **Branch:** `dependabot/npm_and_yarn/object-path-0.11.8` **Commit SHA:** `c4fc63da24129280df3423be24bee7ac19650921` ### Verification performed | Check | Result | |-------|--------| | Fetch latest `master` | ✅ `master` at `6a0f740` (the parent commit of the PR branch) | | Merge conflict check | ✅ **No conflicts** — the PR branch is a clean fast-forward (0 commits behind, 1 commit ahead) | | `object-path` version in `yarn.lock` | ✅ Correctly resolves to `0.11.8` with proper integrity hash | | `git status --short` | ✅ Clean working tree (no unresolved paths) | | `git diff --check` | ✅ No whitespace/conflict-marker issues | | Local vs. remote sync | ✅ Both at `c4fc63d` — already pushed | ### Why no edits were required The Dependabot commit already correctly bumps the indirect dependency `object-path` from `0.11.4` to `0.11.8` in `yarn.lock`. Since `master` is the direct ancestor of this branch, the merge is a trivial fast-forward — there were no conflicts to resolve and no additional changes to make. The PR is **mergeable with `master`** as-is.

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