feat: use puya-ts alpha #40
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joe-p
force-pushed
the
feat/puya-ts-alpha
branch
2 times, most recently
from
9cd62f4 to
9967a2c
Compare
We are pinning to a specific version because it considers beta to be between alpha and 1.0
joe-p
force-pushed
the
feat/puya-ts-alpha
branch
from
9967a2c to
8b66706
Compare
|
We realized we don't have the testing package yet so we'll just tell devs to update to alpha if they want to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes the version used by the template to alpha.
Some context: we are at the EasyA harvard hackathon and want the new inits to use the latest puya TS version since this is what we are going over in the workshop
We felt like updating the template is preferable to doing a beta release so existing template instantiations aren't affected until we are ready for a beta release. Since we are close to release, this seems like a reasonable compromise