DevOps for the v1.14.0 ENSNode release

[tk-o]

Update shared variables

For ALPHA_ACTIVE_PLUGINS, ALPHA-SEPOLIA_ACTIVE_PLUGINS, V2-SEPOLIA_ACTIVE_PLUGINS:

1. Add unigraph plugin.
   • Completed in the Blue env.
   • Completed in the Green env.
2. Drop ensv2 plugin.
   • Completed in the Blue env.
   • Completed in the Green env.

For V2-SEPOLIA_ACTIVE_PLUGINS:

1. Add subgraph plugin.
   • Completed in the Blue env.
   • Completed in the Green env.

[coderabbitai]

🔗 Related PRs

#1570 - deps: fix audit flags [merged]
#1730 - Remove Core Plugin Restriction [merged]
#2128 - The unigraph plugin [merged]
#2145 - fix: use workspace:* versions to enable release [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]

The moment I redeployed the “v2 Sepolia” ENSIndexer with just unigraph and protocol-acceleration plugins activated. The indexing started with no issues:
https://railway.com/project/43d18ce2-788e-4d24-bdae-4a1b6a7a7475/service/060c5b8e-1ed4-4348-92a3-9317646cbd3f?environmentId=713bb7a9-f8dc-4ac6-8060-8976b95e970c&id=a48b611e-c5b3-4d6d-aa6a-7c351d5daf1a#deploy

Therefore, I think we might not be able to activate subgraph and unigraph plugins when indexing the custom Sepolia-fork chain.