Update release.yaml for v1.8

[junkil-park]

Description

Add the v1.8 items to release.yaml

[junkil-park]

@movekevin , @perryjrandall , @thepomeranian , how do we determine what items should go into the upgrade_framework step?

[movekevin]

This doesn't seem valid

[junkil-park]

Changed it to single_sender_authenticator. @davidiw , could you confirm please?

[junkil-park]

For the feature index 33, the const names in Move and Rust are different:

• aptos-core/aptos-move/framework/move-stdlib/sources/configs/features.move

  Line 267 in 957a016

  const SECP256K1_ECDSA_AUTHENTICATOR: u64 = 33;

• aptos-core/types/src/on_chain_config/aptos_features.rs

  Line 43 in 957a016

  SINGLE_SENDER_AUTHENTICATOR = 33,

  
  Is this intended?

[movekevin]

Can you just fix that name on features.move in this same PR @junkil-park 🙏 ? It should say SINGLE_SENDER_AUTHENTICATOR as well

[junkil-park]

Sure, I fixed it in my PR: https://github.com/aptos-labs/aptos-core/pull/10455/files#diff-b408b1036a492541e5ad476af39f23f51018e91ce03a777b1d73654b513baaf3R267 (cc: @movekevin , @davidiw )

[movekevin]

@movekevin , @perryjrandall , @thepomeranian , how do we determine what items should go into the upgrade_framework step?

It's always been the same ones

[movekevin]

cc @igor-aptos do we have a better name/title for this instead of step 1?

[github-actions]

✅ Forge suite compat success on aptos-node-v1.7.2 ==> d9dd3ca27db176750cafd673eecc22994494c417

Compatibility test results for aptos-node-v1.7.2 ==> d9dd3ca27db176750cafd673eecc22994494c417 (PR)
1. Check liveness of validators at old version: aptos-node-v1.7.2
compatibility::simple-validator-upgrade::liveness-check : committed: 3347 txn/s, latency: 6164 ms, (p50: 5100 ms, p90: 9800 ms, p99: 16000 ms), latency samples: 210920
2. Upgrading first Validator to new version: d9dd3ca27db176750cafd673eecc22994494c417
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 1779 txn/s, latency: 16102 ms, (p50: 19200 ms, p90: 22200 ms, p99: 22600 ms), latency samples: 92520
3. Upgrading rest of first batch to new version: d9dd3ca27db176750cafd673eecc22994494c417
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 1774 txn/s, latency: 16323 ms, (p50: 19200 ms, p90: 22300 ms, p99: 22600 ms), latency samples: 92260
4. upgrading second batch to new version: d9dd3ca27db176750cafd673eecc22994494c417
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 3530 txn/s, latency: 8629 ms, (p50: 9900 ms, p90: 11500 ms, p99: 12300 ms), latency samples: 144760
5. check swarm health
Compatibility test for aptos-node-v1.7.2 ==> d9dd3ca27db176750cafd673eecc22994494c417 passed
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite realistic_env_max_load success on d9dd3ca27db176750cafd673eecc22994494c417

two traffics test: inner traffic : committed: 7992 txn/s, latency: 4896 ms, (p50: 4500 ms, p90: 5700 ms, p99: 22700 ms), latency samples: 3452800
two traffics test : committed: 100 txn/s, latency: 2337 ms, (p50: 2100 ms, p90: 2600 ms, p99: 8500 ms), latency samples: 1800
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.204, avg: 0.198", "QsPosToProposal: max: 0.386, avg: 0.184", "ConsensusProposalToOrdered: max: 0.607, avg: 0.579", "ConsensusOrderedToCommit: max: 0.519, avg: 0.489", "ConsensusProposalToCommit: max: 1.106, avg: 1.068"]
Max round gap was 1 [limit 4] at version 1883336. Max no progress secs was 4.162989 [limit 10] at version 1883336.
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite framework_upgrade success on aptos-node-v1.7.2 ==> d9dd3ca27db176750cafd673eecc22994494c417

Compatibility test results for aptos-node-v1.7.2 ==> d9dd3ca27db176750cafd673eecc22994494c417 (PR)
Upgrade the nodes to version: d9dd3ca27db176750cafd673eecc22994494c417
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 4319 txn/s, latency: 4792 ms, (p50: 4800 ms, p90: 7700 ms, p99: 8100 ms), latency samples: 241880
5. check swarm health
Compatibility test for aptos-node-v1.7.2 ==> d9dd3ca27db176750cafd673eecc22994494c417 passed
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Test runner output
• Test run is land-blocking

[junkil-park]

Migrates to #10679