Skip to content

feat(versioning): added api deployment versioning, change detection in workflow, added ci job to run migrations on merge to main#220

Merged
waleedlatif1 merged 8 commits intomainfrom
feat/versioning
Apr 3, 2025
Merged

feat(versioning): added api deployment versioning, change detection in workflow, added ci job to run migrations on merge to main#220
waleedlatif1 merged 8 commits intomainfrom
feat/versioning

Conversation

@waleedlatif1
Copy link
Collaborator

  • added initial code for versioning
  • ran migrations & improvements to versioning
  • change sensitivity of state diff checker
  • debounce the change detection function
  • cleaned up file structure
  • added ci job to run migrations when merging to main
  • ran migrations

Description

added api deployment versioning, change detection in workflow. This way, the user knows whether the API they need to invoke is the same or different from what they see on the canvas at any given time. In the future, I imagine we can also allow them to just go back to the delpoyed state or at least see the differences.

Also added ci job to run migrations when we merge to main

Fixes #82

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Tested extensively locally. Tried many different things and we count anything that impacts execution as a 'change', we ignore positioning and edge length, but everything else impacts the execution so we let the user know.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added tests that prove my fix is effective or that my feature works
  • All tests pass locally and in CI (npm test)
  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules
  • I have updated version numbers as needed (if needed)

Security Considerations:

  • My changes do not introduce any new security vulnerabilities
  • I have considered the security implications of my changes

@cubic-dev-ai
Copy link

cubic-dev-ai bot commented Apr 3, 2025

Review this PR on mrge.io

@vercel
Copy link

vercel bot commented Apr 3, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 3, 2025 5:20am
sim ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 3, 2025 5:20am

@waleedlatif1 waleedlatif1 merged commit 9d3b270 into main Apr 3, 2025
6 checks passed
@waleedlatif1 waleedlatif1 deleted the feat/versioning branch April 3, 2025 20:19
RadoBoiii pushed a commit to RadoBoiii/sim-fork that referenced this pull request Apr 13, 2025
…n workflow, added ci job to run migrations on merge to main (simstudioai#220)

* added initial code for versioning

* ran migrations & improvements to versioning

* change sensitivity of state diff checker

* debounce the change detection function

* cleaned up file structure

* added ci job to run migrations when merging to main

* ran migrations

* cleanup unused files, remove unused dependencies
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.

1 participant