Bump moment from 2.24.0 to 2.29.4 in /ghost/versions/3.0.2 #32
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/rileysblog!32
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "dependabot/npm_and_yarn/ghost/versions/3.0.2/moment-2.29.4"
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 moment from 2.24.0 to 2.29.4.
Changelog
Sourced from moment's changelog.
... (truncated)
Commits
000ac18Build 2.24.4f2006b6Bump version to 2.24.4536ad0cUpdate changelog for 2.29.49a3b589[bugfix] Fix redos in preprocessRFC2822 regex (#6015)6374fd8Merge branch 'master' into developb4e6153Revert "[bugfix] Fix redos in preprocessRFC2822 regex (#6015)"7aebb16[bugfix] Fix redos in preprocessRFC2822 regex (#6015)57c9062Build 2.29.3aaf50b6Fixup release complaints26f4aefBump version to 2.29.3Dependabot 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 #32 on branch
dependabot/npm_and_yarn/ghost/versions/3.0.2/moment-2.29.4. 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 the relevant files.
Let me check the moment version and current branch state.
The
package.jsonalready showsmoment: 2.29.4. Now let me check the yarn.lock and fetch the latest master.Let me look at the yarn.lock entries for moment and fetch master to check for conflicts.
Now let me merge master into the PR branch and check for conflicts.
origin/masterisn't set as a tracking ref. I'll merge FETCH_HEAD directly.The
git statusis timing out due to the repo size. Let me verify state differently.Master is already an ancestor of the current HEAD. The branch is fully up to date with master and the merge reported "Already up to date." Now let me verify the moment version is correctly set and check there are no conflict markers.
No conflict markers. Let me confirm the key changes are in place and verify the commit is pushed.
The state looks complete. Let me verify there's nothing uncommitted and confirm local matches remote.
Everything checks out. Let me do a final verification that the working tree is clean for the changed files.
Everything is verified and complete. Here's the summary:
Summary
PR #32 ("Bump moment from 2.24.0 to 2.29.4 in /ghost/versions/3.0.2") is already in a mergeable state.
Checks performed:
masterand merged it into the PR branch. Result: "Already up to date" —masteris an ancestor of the current HEAD (git merge-base --is-ancestorconfirmed).package.jsonandyarn.lockfor conflict markers (<<<<<<<,=======,>>>>>>>) — none found.origin/dependabot/.../moment-2.29.4.Change verification:
ghost/versions/3.0.2/package.json:"moment": "2.29.4"✅ghost/versions/3.0.2/yarn.lock:moment@2.29.4entry present with correct resolved URL and integrity hash; old2.24.0entry retained as it's pinned by a transitive dep (deduplicated to 2.29.4 via the merged descriptor key).No new commit was needed — the existing branch was already up to date with
masterand the version bump was correctly applied. The branch is mergeable.dependabot/npm_and_yarn/ghost/versions/3.0.2/moment-2.29.4c4eb8fb7b0a63c49c7b336d467aa3d855598e712mergeable=True, mergeable_state=clean)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.