Skip to content

Conversation

RensR
Copy link
Collaborator

@RensR RensR commented Oct 8, 2025

Preps 1.6.3 which only includes the FeeQuoter. It bumps all pools on 1.6.3-dev to 1.6.4-dev.

This PR adds the compiled bytecode from gethwrappers to NPM releases. It copies the bytecode by traversing the AST. This process does not impact any devex as it only happens during package cuts.

PR blocked by the merger of 1.6.3 FeeQuoter #1217

"@chainlink/contracts-ccip": patch
---

Rate limits are now applied on the dest denomination for releaseOrMint calls
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Old changesets should have been consumed long ago. Removing them now

@RensR RensR force-pushed the prep-rlease branch 2 times, most recently from 9dbfd86 to a60edd2 Compare October 8, 2025 17:00
@RensR RensR marked this pull request as ready for review October 8, 2025 17:05
@RensR RensR requested a review from a team as a code owner October 8, 2025 17:05
_assertFeeQuoterStaticConfigsEqual(s_feeQuoter.getStaticConfig(), staticConfig);
assertEq(feeTokens, s_feeQuoter.getFeeTokens());
assertEq(priceUpdaters, s_feeQuoter.getAllAuthorizedCallers());
assertEq(s_feeQuoter.typeAndVersion(), "FeeQuoter 1.6.3-dev");
Copy link
Collaborator

Choose a reason for hiding this comment

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

huh! I'm surprised this didn't fail the test coverage check, I recall we were 1 line away from failing, did something change there

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think it doens't count constant strings as lines of code to be tested. I really dislike these types of assertions (constant == constant) as they only cause churn during updates.

matYang
matYang previously approved these changes Oct 8, 2025
matYang
matYang previously approved these changes Oct 8, 2025
@matYang
Copy link
Collaborator

matYang commented Oct 8, 2025

since we are at it, shall we include abi versioning as well

i.e. from

generated/v1_2_3/contract_name/wrapper.go -> bytecode/v1_2_3/contract_name/binary.bin

to

generated/v1_2_3/contract_name/wrapper.go -> release-artifacts/v1_2_3/contract_name/binary.bin
                                             release-artifacts/v1_2_3/contract_name/abi.json

// Determine the base output path - flatten to version/filename structure
relPath, err := filepath.Rel(gobindingsDir, path)
if err != nil {
return fmt.Errorf("failed to get relative path: %w", err)
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
return fmt.Errorf("failed to get relative path: %w", err)
return fmt.Errorf("failed to get relative path for %s: %w", path, err)

0xsuryansh
0xsuryansh previously approved these changes Oct 9, 2025
func processGoFile(path, gobindingsDir, bytecodeDir, abiDir string) error {
// Extract metadata from the file
metadata, err := extractMetadata(path)
if err != nil {
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: feels safer to fail the generation process if there is error here, or metadata.Bytecode == "", or metadata.ABI == "", to ensure there is always valid bin and abi for every contract wrapper, as opposed to failing silently cuz no one checks CI output

matYang
matYang previously approved these changes Oct 9, 2025
@RensR RensR dismissed stale reviews from matYang and 0xsuryansh via 70a6cb7 October 9, 2025 16:31
@matYang matYang enabled auto-merge October 9, 2025 16:36
Copy link

github-actions bot commented Oct 9, 2025

Metric prep-rlease main
Coverage 69.4% 69.0%

@matYang matYang added this pull request to the merge queue Oct 9, 2025
Merged via the queue into main with commit 83feddc Oct 9, 2025
51 checks passed
@matYang matYang deleted the prep-rlease branch October 9, 2025 17:05
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.

4 participants