Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pin dugite to 2.1.0 #7

Merged
merged 1 commit into from
Dec 2, 2023
Merged

Pin dugite to 2.1.0 #7

merged 1 commit into from
Dec 2, 2023

Conversation

confused-Techie
Copy link
Member

This PR pins dugite to 2.1.0. Really only because this is the same version pinned within the github package.

Which is used by this dep, and we would like to sync these two deps perfectly to reduce the amount of times that dugite is installed into Pulsar

DeeDeeG pushed a commit that referenced this pull request Nov 14, 2023
---

^ Original commit by confused-Techie on a PR branch.

Committer notes (these notes are written by DeeDeeG):

(cherry picked from commit dab6bd8)

Cherry-picking #7
on a dedicated branch, since the `superstring` stuff is taking
longer than expected, and this is a way to get just the `dugite`
syncing/deduping landed at core repo faster, without waiting on the
similarly motivated but separate `superstring` stuff I was doing.

(Needs to be done on a separate branch to avoid either a really wacky
commit history on `master` branch, with reverts and revert-reverts,
or going with the "nuclear option" and force pushing to `master`
branch after commits have been live there for multiple days.)
@DeeDeeG
Copy link
Member

DeeDeeG commented Dec 2, 2023

Merging this, since we've been using this change in Pulsar core for a bit now.

I think we can try bumping again to even newer Dugite, ahead of the upcoming Regular release. But it may as well be a follow-up PR, so merging this one as-is.

Doesn't matter a ton if we're about to bump, but this belongs in the commit history of the default branch, IMO.

Thanks again for working on all this!

@DeeDeeG DeeDeeG merged commit f4bcc71 into master Dec 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants