Need a way to go back to previous version of internal Library.
Sometime a small modification of the library work fine for the current app, but then we discover that it doesn’t work as expected in an other app.
Hi @jlboutin60,
This is a very common challenge when sharing internal libraries across multiple apps. Here are a few approaches that can help until Scriptcase adds native versioning support:
-
Manual versioning with naming conventions — Append a version suffix to your library files (e.g.,
mylib_v1,mylib_v2). Each app references the specific version it was tested with. Simple but effective. -
Git or version control — If you’re not already using Git, keeping your library code in a repository lets you tag versions, compare changes, and roll back when something breaks.
-
Changelog discipline — Maintain a simple changelog file alongside your library. Before modifying anything, document what you’re changing and which apps depend on the current behavior.
-
Separate dev/staging environment — Test library changes against all dependent apps before pushing to production. This catches cross-app regressions early.
I agree that built-in library versioning in Scriptcase would be a great feature. +1 for this suggestion!
Best regards
Thank you,
Git control work fine with External libraries but Internal libraries control is kept in the DB, you cannot simply restore them, like with the external one