DevOps for the v1.10.0 ENSNode release

[lightwalker-eth]

• Parallel Inclusion of ensv2 and subgraph plugins in Railway ENSIndexers #1895
• Update the CUSTOM_REFERRAL_PROGRAM_EDITIONS environment variable in ENSApi so that it points to https://ensawards.org/production-editions-v1.10.0.json as the data schema will have breaking changes in v1.10.0.
  • Related background info: Proactively update production referral rules config formatted for the next ENSNode v1.10.0 release #1902
• Rename CUSTOM_REFERRAL_PROGRAM_EDITIONS to REFERRAL_PROGRAM_EDITIONS in ENSApi.
  • Related background info: Remove "default" referral program rule set #1905

[coderabbitai]

🔗 Related PRs

#1570 - deps: fix audit flags [merged]
#1768 - fix(deps): resolve undici and yauzl security vulnerabilities [merged]
#1823 - chore(ens-referrals): Update ens-referrals README.md [merged]
#1849 - chore(ens-referrals): Update readme [merged]
#1912 - Removing Default Referral Program Rule Set [merged]
#1938 - Using NormalizedAddress in referral program logic [merged]
#1986 - Prevent overlapping referral program editions [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[tk-o]

@lightwalker-eth as for issue:

• Parallel Inclusion of ensv2 and subgraph plugins in Railway ENSIndexers #1895

following a comment from @shrugs that says:

blue alpha ensv2 plugin disabled in 1.10 due to slowness

Am I correct to assum we also don't want enable ensv2 plugin across all ENSIndexer instances in the Green env for the v1.10.1 release?

[lightwalker-eth]

@tk-o Yes, confirmed let's not enable the ensv2 plugin on any instances operating in the mainnet namespace on the v1.10.x release of ENSNode. However we should enable both ensv2 and subgraph on all alpha-sepolia and sepolia-v2 instances.

@tk-o Could you please create a GitHub new issue for "DevOps for the v1.11.0 ENSNode release" and initialize the description of that issue with any environment variable updates that should be done? I see that @shrugs has found solutions to the ensv2 plugin slowness which will be fixed when we make the v1.11.0 release. Please help us remember which instances in which environments should have environment variable updates applied. The only instances that should NOT have both ensv2 and subgraph plugins activated are the instances we have that maximize for backwards compatibility with the ENS Subgraph.

[tk-o]

Confirming that for the Green env, I have enabled:

• ensv2 plugin for ENSIndexer Alpha Sepolia instance
• subgraph plugin for ENSIndexer V2 Sepolia instance

[tk-o]

@lightwalker-eth here's the follow up issue for v1.11:

• DevOps for the v1.11.0 ENSNode release #2025