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

gomod: update go mod using go work sync #946

Merged
merged 3 commits into from
Aug 22, 2024

Conversation

yyforyongyu
Copy link
Collaborator

@yyforyongyu yyforyongyu commented Aug 14, 2024

Sync versions across repos.

Depends on

@Roasbeef
Copy link
Member

Hmm, I think we might need to do this in stages so we can tag new versions of the various sub-modules incrementally.

@yyforyongyu yyforyongyu force-pushed the update-gomod branch 3 times, most recently from d5f208d to bdef8c4 Compare August 21, 2024 06:50
@guggero guggero self-requested a review August 21, 2024 07:12
@yyforyongyu yyforyongyu force-pushed the update-gomod branch 4 times, most recently from a2c1215 to 906d381 Compare August 21, 2024 08:38
Copy link
Collaborator

@guggero guggero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yayy, green CI. Thanks for the update!

Makefile Outdated Show resolved Hide resolved
.golangci.yml Outdated

issues:
# Only check issues in the new code.
new-from-rev: HEAD~1
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't this cause to only look at code in the very last commit? Shouldn't we pin this to a fixed version and update every once in a while?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah was experimenting sth...basically I was trying to use new-from-rev: master - the idea is to only lint the diff between the current PR and the master, but couldn't get it to work due to this error,

level=warning msg="[runner] Can't process result by diff processor: can't prepare diff by revgrep: could not read git repo: error executing \"git diff --color=never --no-ext-diff --default-prefix --relative master --\": exit status 128: fatal: bad revision 'master'\n"

seems to be a revgrep.go issue.

Changed to commit instead.

@guggero
Copy link
Collaborator

guggero commented Aug 21, 2024

Oops, I just realized that all my comments should've been in #947...

@guggero
Copy link
Collaborator

guggero commented Aug 22, 2024

Can be rebased. Pushed the following tags:

To github.com:btcsuite/btcwallet.git
 * [new tag]           wallet/txauthor/v1.3.5 -> wallet/txauthor/v1.3.5
 * [new tag]           wallet/txrules/v1.2.2 -> wallet/txrules/v1.2.2
 * [new tag]           wallet/txsizes/v1.2.5 -> wallet/txsizes/v1.2.5
 * [new tag]           walletdb/v1.4.3 -> walletdb/v1.4.3

@guggero guggero merged commit 66377c1 into btcsuite:master Aug 22, 2024
3 checks passed
@yyforyongyu yyforyongyu deleted the update-gomod branch August 22, 2024 15:11
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.

3 participants