Bump loader-utils from 1.1.0 to 1.4.2 #36
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
riley/gatsbyblog!36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "dependabot/npm_and_yarn/loader-utils-1.4.2"
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?
Bumps loader-utils from 1.1.0 to 1.4.2.
Release notes
Sourced from loader-utils's releases.
... (truncated)
Changelog
Sourced from loader-utils's changelog.
... (truncated)
Commits
331ad50chore(release): 1.4.217cbf8ffix: ReDoS problem (#226)8f082b3chore(release): 1.4.14504e34fix: security problem (#220)d95b8b5chore(release): 1.4.0cd0e428feat: theresourceQueryis passed to theinterpolateNamemethod (#163)06d36cfchore(release): 1.3.0469eebafeat: support the[query]template for theinterpolatedNamemethod (#162)909c99dchore: funding.yml config and CI fix (#159)b5b74f0Set up CI with Azure PipelinesMaintainer changes
This version was pushed to npm by evilebottnawi, a new releaser for loader-utils 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.
🛠️ CodeTether Fix
Picked up this request for PR #36 on branch
dependabot/npm_and_yarn/loader-utils-1.4.2. 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 withmaster.🛠️ CodeTether Fix
I'll start by examining the current state of the repository and understanding what needs to change.
loader-utilsis not a direct dependency—it's transitive. Let me check how it appears in the lockfile and whether the PR branch already changed it.The PR branch already has loader-utils at 1.4.2 in the lockfile. Now let me check the state relative to master and whether there are any merge conflicts.
Master has no commits that aren't already in the PR branch. The PR branch is already based on the latest master. Let me perform the merge to confirm mergeability, then verify.
Already up to date — no conflicts. Now let me run the final checks:
git diff --checkand confirm the loader-utils bump is complete and correct.The diff shows the loader-utils bump and associated lockfile changes (including
http→httpsregistry normalization and removal of the now-unusedbig.js@^3.1.3which was a dep of the old version). Let me verify the loader-utils entry on master vs current to confirm the bump is correct and complete.The bump is correctly applied and complete. Let me do final validation — confirm package.json is valid, the working tree is clean, and the branch is pushed.
Everything is already in the correct, mergeable state. Here's the summary:
Task Complete ✅
Branch:
dependabot/npm_and_yarn/loader-utils-1.4.2→masterWhat I verified and did:
Fetched latest
master— master has no commits that aren't already in the PR branch, so the PR branch is already based on the latest base.Merged master into the PR branch — Git reported "Already up to date." No conflicts to resolve.
Confirmed the loader-utils bump is correct:
yarn.locknow hasloader-utils@^1.0.2, loader-utils@^1.1.0, loader-utils@^1.2.3:all resolved toversion "1.4.2"(with theintegritysha512 hash).loader-utils@^1.2.3→1.2.3entry was consolidated.big.js@^3.1.3dependency (a transitive dep of the old 1.1.0 version) was removed.loader-utilsis a transitive dependency only;package.jsoncorrectly does not list it directly.Pre-commit checks all pass:
git status --short→ clean (no unresolved paths)git diff --check→ no whitespace/conflict-marker errorspackage.json→ valid JSONNo new commit was needed — the branch was already correctly populated by Dependabot and is in sync with
origin/dependabot/npm_and_yarn/loader-utils-1.4.2. The PR is mergeable withmaster(mergeable_state=clean).Existing commit:
d49692b— "Bump loader-utils from 1.1.0 to 1.4.2"View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.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.