7 commits

Author	SHA1	Message	Date
Arran Schlosberg	51afedec91	chore: Go 1.24 (#232) ... ## Why this should be merged Version increase across all `ava-labs` EVM-related code. ## How this works Bump to 1.24.8 in both `go.mod` files + requisite version increase for `golangci-lint`. ## How this was tested Existing tests. --------- Co-authored-by: Austin Larson <austin.larson@avalabs.org>	2025-10-13 14:07:33 -04:00
Arran Schlosberg	d4c22ca34b	chore: stochastic gradient descent to fix goheader (#196) ... ## Why this should be merged Avoids false positives from `goheader`. ## How this works Checks out entire history to give the linter a reference point for new issues only. ## How this was tested With great frustration by waiting for CI.	2025-06-23 15:52:20 +00:00
Arran Schlosberg	0ed61356ed	refactor(params): make LibEVMVersion a constant (#162) ... > [!NOTE] > This will be merged into `main` once the current target branch has been merged. ## Why this should be merged My original implementation was back to front and it's been bugging me. ## How this works Originally `params.LibEVMVersion` was a `var` (because it needed to be computed) and the test used a `const`. This change simply inverts the two and moves some code around without any change in logic. I bumped the minor version to 2 (a no-op when not on a release branch) to bring it in line with the latest release candidate and to avoid forgetting to do so when performing an actual release. ## How this was tested Unit test of version-string constant.	2025-03-17 19:29:16 +00:00
Arran Schlosberg	b0332b5168	chore(ci): add merge_group trigger to required workflows (#160) ... ## Why this should be merged Allows ruleset-required workflows to be triggered by a merge queue, not just the PR for the merge. Although `main` isn't a particularly "busy" branch, a merge queue will ensure that CI passes on the exact version of code that is about to be merged; i.e. (from the [docs]): > The merge queue provides the same benefits as the **Require branches to be up to date before merging** branch protection, but does not require a pull request author to update their pull request branch and wait for status checks to finish before trying to merge. [docs]: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue#about-merge-queues ## How this works Adds `merge_group` workflow trigger with [recommended type](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#merge_group). ## How this was tested N/A (worst-case it has to be reverted and another PR is temporarily blocked).	2025-03-11 13:57:57 +00:00
Quentin McGaw	1344d20908	chore(ci): disable lint goheader step on non-pull-request events (#143) ... - Pin golangci-lint action to v6 now that goheader doesn't run on the default branch pushes - This addresses the goheader step misbehaving and linting all files on pushes	2025-02-17 11:34:52 +00:00
Arran Schlosberg	f7a3a4f548	chore(ci): add go catch-all job (#140) ... ## Why this should be merged New jobs are easily forgotten in the GitHub rules so we will only gate on `go` and have all others added as dependencies. ## How this works Same as #139 ## How this was tested Inspection of CI run: 	2025-02-14 12:56:51 -05:00
Arran Schlosberg	bc42e5f29c	chore(ci): consolidate linters (#139) ... ## Why this should be merged Branch-protection rules only require the Go linter (erroneously called `lint`) by mistake. All linters are now dependencies of a single `lint` job that remains as a PR gate. New linters will now be enforced by default. Closes #138 ## How this works GitHub Actions `need` configuration. The path limitation of running `yamllint` is removed because it's such a cheap job so is ok to always run. ## How this was tested Inspection of CI run and PR's required jobs:  	2025-02-14 11:48:55 -05:00

Renamed from .github/workflows/golangci-lint.yml (Browse further)