Skip to content

update chain-selectors to v1.0.81#571

Merged
graham-chainlink merged 1 commit into
mainfrom
update-chain-selectors-1.0.81
Nov 12, 2025
Merged

update chain-selectors to v1.0.81#571
graham-chainlink merged 1 commit into
mainfrom
update-chain-selectors-1.0.81

Conversation

@jkongie

@jkongie jkongie commented Nov 12, 2025

Copy link
Copy Markdown
Collaborator

No description provided.

@jkongie jkongie requested a review from a team as a code owner November 12, 2025 10:06
@changeset-bot

changeset-bot Bot commented Nov 12, 2025

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 6a6b5e1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
chainlink-deployments-framework Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions

Copy link
Copy Markdown

👋 jkongie, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

@jkongie jkongie force-pushed the update-chain-selectors-1.0.81 branch from f52c3fb to 6a6b5e1 Compare November 12, 2025 10:11
@jkongie jkongie requested a review from a team as a code owner November 12, 2025 10:11
@cl-sonarqube-production

Copy link
Copy Markdown

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@graham-chainlink

Copy link
Copy Markdown
Collaborator

merging this as i am going to perform a release :D

@graham-chainlink graham-chainlink added this pull request to the merge queue Nov 12, 2025
Merged via the queue into main with commit 8db262d Nov 12, 2025
15 checks passed
@graham-chainlink graham-chainlink deleted the update-chain-selectors-1.0.81 branch November 12, 2025 12:55
github-merge-queue Bot pushed a commit that referenced this pull request Nov 12, 2025
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## chainlink-deployments-framework@0.66.0

### Minor Changes

-
[#571](#571)
[`8db262d`](8db262d)
Thanks [@jkongie](https://github.com/jkongie)! - Bump chain-selectors
package to v1.0.81

### Patch Changes

-
[#570](#570)
[`eb74395`](eb74395)
Thanks [@skudasov](https://github.com/skudasov)! - Adds a new EVM
Confirm Functor which allows the user to specify a custom wait interval
for checking confirmation.
    Example

    ```golang
    		p, err := cldf_evm_provider.NewRPCChainProvider(
    			d.ChainSelector,
    			cldf_evm_provider.RPCChainProviderConfig{
    				DeployerTransactorGen: cldf_evm_provider.TransactorFromRaw(
    					getNetworkPrivateKey(),
    				),
    				RPCs: []rpcclient.RPC{
    					{
    						Name:               "default",
    						WSURL:              rpcWSURL,
    						HTTPURL:            rpcHTTPURL,
    						PreferredURLScheme: rpcclient.URLSchemePreferenceHTTP,
    					},
    				},
    				ConfirmFunctor: cldf_evm_provider.ConfirmFuncGeth(
    					30*time.Second,
// set custom confirm ticker time because Anvil's blocks are instant
    					cldf_evm_provider.WithTickInterval(5*time.Millisecond),
    				),
    			},
    		).Initialize(context.Background())
    ```

---------

Co-authored-by: app-token-issuer-engops[bot] <144731339+app-token-issuer-engops[bot]@users.noreply.github.com>
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