Skip to content

chore(deps): update codecov/codecov-action action to v7#366

Open
renovate[bot] wants to merge 2 commits into
v0.40-devfrom
renovate/codecov-codecov-action-7.x
Open

chore(deps): update codecov/codecov-action action to v7#366
renovate[bot] wants to merge 2 commits into
v0.40-devfrom
renovate/codecov-codecov-action-7.x

Conversation

@renovate

@renovate renovate Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
codecov/codecov-action action major v5.4.3 → v7.0.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

codecov/codecov-action (codecov/codecov-action)

v7.0.0

Compare Source

⚠️ Due to migration issues with keybase, we are unable to update our keys under the codecovsecurity account. We have deleted the account and are using codecovsecops with the original gpg key

What's Changed

Full Changelog: codecov/codecov-action@v6.0.1...v7.0.0

v7

Compare Source

v6.0.2

Compare Source

This is a copy of the v7.0.0 release to make updates easier

What's Changed

Full Changelog: codecov/codecov-action@v6.0.1...v6.0.2

v6.0.1

Compare Source

What's Changed

Full Changelog: codecov/codecov-action@v6.0.0...v6.0.1

v6.0.0

Compare Source

⚠️ This version introduces support for node24 which make cause breaking changes for systems that do not currently support node24. ⚠️
What's Changed

Full Changelog: codecov/codecov-action@v5.5.4...v6.0.0

v6

Compare Source

v5.5.5

Compare Source

This release only contains the keybase.io change as described here.

Full Changelog: codecov/codecov-action@v5.5.4...v5.5.5

v5.5.4

Compare Source

This is a mirror of v5.5.2. v6 will be released which requires node24

What's Changed

Full Changelog: codecov/codecov-action@v5.5.3...v5.5.4

v5.5.3

Compare Source

What's Changed

Full Changelog: codecov/codecov-action@v5.5.2...v5.5.3

v5.5.2

Compare Source

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.5.1..v5.5.2

v5.5.1

Compare Source

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.5.0..v5.5.1

v5.5.0

Compare Source

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.4.3..v5.5.0

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

MuncleUscles and others added 2 commits July 8, 2026 22:58
@MuncleUscles @renovate
@Tobu8888 @acastellana @claude
chore: fast-forward main to v0.40-dev (#365)
c7ef3ea 
* fix(system): propagate command-check and version parse fixes to v0.40-dev (#350)

Propagates #349 to v0.40-dev.

* docs: add branching guide (#353)

* docs: add branching guide

* ci: harden testnet smoke timeout

* feat: support fee profiles in contract commands (#355)

* feat: support fee profiles in contract commands

* test: make fee profile deploy test portable

* feat: staking validators discovery (#357)

* feat: add staking validators discovery

* feat: epoch-aware validator listing with below-min indicator

* fix(staking): account-less client for read-only staking queries

getReadOnlyStakingClient threw 'Account not found' on fresh installs;
listings and other reads don't need a local account.

* feat: vesting commands (#358)

* feat: add vesting commands

* feat(vesting): validator subcommands — create/join, deposit, exit, claim, operator-transfer, set-identity, list/status

Drives the CON-607 Vesting.sol validator leg through the SDK's named
vestingValidator* actions; list/status enumerate getValidatorWallets
with per-wallet deposited principal.

* chore(deps): update dependency uuid to v11.1.1 [security] (#320)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

* fix(init): use backend provider id "google" for Gemini (#359)

Selecting Gemini during `genlayer init` failed with:
  Requested providers '{'geminiai'}' do not match any stored providers.

The selected provider id is forwarded verbatim to
sim_createRandomValidators, but the backend's llm_provider table stores
Gemini as "google". Rename the provider id geminiai -> google so it
matches. Display name ("Gemini") and env var (GEMINI_API_KEY) are
unchanged.

Since "geminiai" never resolved to a valid provider, no working
configuration relied on it.

Fixes #271

Co-authored-by: Edgars Nemše <edgars@genlayerlabs.com>

* fix(docs-sync): stop overwriting the generated root _meta.json (#352)

The sync-docs workflow rsynced the generated category-based
docs/api-references/_meta.json into genlayer-docs and then immediately
overwrote it with a hardcoded heredoc containing the pre-grouping flat
command list (init, up, deploy, ...). Those keys no longer match the
directory layout, so the genlayer-docs sidebar rendered broken entries
on every sync (fixed manually in genlayer-docs#426; this removes the
cause).

Also make the generated root meta complete:
- add "index": "Overview" for the generated index.mdx
- append ungrouped top-level commands (estimate-fees, finalize,
  finalize-batch) so they get explicit nav entries instead of relying
  on Nextra's implicit append

Snapshot under docs/api-references regenerated against current main
(picks up the new estimate-fees command and latest help text).

Co-authored-by: Albert Castellana <albert@genlayer.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Edgars <edgars@entropicsolutions.io>

* fix: drop getSlashingAddress from validator-history (#361)

getSlashingAddress() was removed from the genlayer-js SDK (v0.39+/v2-dev),
causing `genlayer staking validator-history` to crash with
`client.getSlashingAddress is not a function` before any history is fetched.

Resolve the idleness (slashing) contract address dynamically via viem
readContract against consensusMainContract.getIdlenessAddress(), falling
back to the staking contract address if resolution fails so reward events
still display.

Port of #344 (by @ygd58) from the dead v0.39 line to v0.40-dev.
Supersedes #344.

Fixes #341

Co-authored-by: Edgars <edgars@entropicsolutions.io>

* feat(network): custom network profiles with deployment-file import (#362)

* feat(network): custom network profiles with deployment-file import

genlayer network add <alias> --base <built-in> [--deployment <json>]
[--rpc <url>] [--consensus-main|--consensus-data|--staking|--fee-manager
|--rounds-storage|--appeals <addr>] [--chain-id <n>] [--deployment-key <path>]

Profiles persist as base + address overrides only; resolveNetwork loads
the base chain fresh from genlayer-js and applies overrides, so ABIs
never go stale. network set/list/info/remove and StakingAction --network
accept custom aliases. The consensus deployments.json shape is parsed by
walking the tree for ContractName->address leaves (ConsensusMain,
ConsensusData, GenStaking/Staking, FeeManager, Rounds/RoundsStorage,
Appeals); flags take precedence over the file. Adds a prepare script so
npm install from a git ref builds dist. Verified: 576 vitest tests, full
manual smoke (add/list/set/info/remove with a deployment file).

* chore(deps): bump genlayer-js to v2-dev tip for vesting actions

The locked v2-dev SHA (28e99fbc) predates the vesting client actions;
vestingValidatorJoin and friends land at 666d1156. Verified live:
vesting validator create succeeds against a #1162-branch consensus
deployment.

* docs(cli): regenerate API references; fix option placeholder regex

The docs generator's option regex only matched <word> placeholders, so
flags with dots or hyphens in the value name (--base <built-in-alias>,
--deployment <path.json>, --deployment-key <dot.path>) were silently
dropped from the options tables. Widen to <[^>]+> and regenerate: adds
the network add/remove pages and the previously undocumented vesting
command section (validator create/deposit/exit/claim, operator-transfer,
set-identity, delegate/undelegate/claim/withdraw/list).

* fix(vesting): resolve validator wallet address in create output

The join receipt does not carry the new wallet address, so the output
printed validatorWallet: undefined. Read getValidatorWallets from the
vesting contract after the join and report the newest entry. Verified
live against a #1162-branch deployment.

* fix: make git install build lifecycle robust (#363)

* fix: make git install build script self contained

* chore: refresh genlayer-js lockfile

* fix: make keychain dependency optional

* fix: restore git prepare build

* fix: include build dependency for git installs

* chore: keep esbuild as dev dependency

* ci: publish prereleases to npm dist tags (#364)

* ci: add clarke cli tarball release

* ci: publish prereleases to npm dist tags

* Release v0.40.0-rc1 [skip ci]

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Tobu <36818942+Tobu8888@users.noreply.github.com>
Co-authored-by: Albert Castellana <acastellana@users.noreply.github.com>
Co-authored-by: Albert Castellana <albert@genlayer.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Edgars <edgars@entropicsolutions.io>
@renovate
chore(deps): update codecov/codecov-action action to v7
29f391a
@github-actions github-actions Bot changed the base branch from main to v0.40-dev July 8, 2026 21:59
@github-actions

github-actions Bot commented Jul 8, 2026

Copy link
Copy Markdown

This PR targeted main, which is only the default/static branch.

I retargeted it to v0.40-dev, the active development branch. Pushes to v0.40-dev automatically fast-forward main.

@renovate

renovate Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@MuncleUscles