With the new release of Gramine, old packages are replaced with new packages which use to cause verifier's build failure.
We always needed a PR to fix it after every Gramine release.
This issue was fixed partially with PR #82 where Gramine would use latest release package but GSC is still on old release.
Curated apps would still fail if GSC and Gramine versions are not same and also not compatible.
This PR tries to minimize the difference in releases of GSC and Gramine as latest tags are fetched automatically.
There could be the issue again if there is a time gap in creating the latest release tags for Gramine and GSC and in that time if a user curate the apps. We can think of placing a policy for creating Gramine and GSC tags at the same time.
After this PR, we won't need a contrib PR again and again after every Gramine releasefor moving to the latest Gramine release.
With the new release of Gramine, old packages are replaced with new packages which use to cause verifier's build failure.
We always needed a PR to fix it after every Gramine release.
This issue was fixed partially with PR #82 where Gramine would use latest release package but GSC is still on old release.
Curated apps would still fail if GSC and Gramine versions are not same and also not compatible.
This PR tries to minimize the difference in releases of GSC and Gramine as latest tags are fetched automatically.
There could be the issue again if there is a time gap in creating the latest release tags for Gramine and GSC and in that time if a user curate the apps. We can think of placing a policy for creating Gramine and GSC tags at the same time.
After this PR, we won't need a contrib PR again and again after every Gramine releasefor moving to the latest Gramine release.
This change is