Skip to content

Conversation

@josephjclark
Copy link
Collaborator

A rewrite of the version hash algorithm to better align with Lightning

I am now convinced that lightning and the CLI MUST generate identical hashes, otherwise we can't really work out what's changed when deploying.

The basic strategy here is, rather than use the Project structure to generate the hash, convert to app state and use that. This means we're much more closer to the lightning structure, and it's a lot easier to compare the algos.

Fixes #1078

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to know!):

  • Code generation (copilot but not intellisense)
  • Learning or fact checking
  • Strategy / design
  • Optimisation / refactoring
  • Translation / spellchecking / doc gen
  • Other
  • I have not used AI

You can read more details in our Responsible AI Policy

- Don't include keys in the hash
- Fixes for edges and triggers
This aligns the implementation a lot closer to lightnign

A couple of fixes in support of this
@josephjclark josephjclark changed the base branch from main to version-history-fix January 23, 2026 17:31
@github-project-automation github-project-automation bot moved this to New Issues in v2 Jan 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: New Issues

Development

Successfully merging this pull request may close these issues.

CLI and App version hashes are not the same

2 participants