Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't download the published version of Tact in CI #1810

Open
novusnota opened this issue Feb 13, 2025 · 1 comment
Open

Don't download the published version of Tact in CI #1810

novusnota opened this issue Feb 13, 2025 · 1 comment
Assignees
Labels
scope: ci Continuous Integration: GitHub Actions (.github), commit/push hooks (.husky)

Comments

@novusnota
Copy link
Member

novusnota commented Feb 13, 2025

Instead, we need to use the main branch and always link with it. This is important for reducing the npm download count from the usage of tact-template and Blueprint in the test suite.

That said, the command for creating a Blueprint project might have to be changed, otherwise it'll still download the Tact compiler there no matter what we do. This part is a blocker.

@novusnota novusnota added the scope: ci Continuous Integration: GitHub Actions (.github), commit/push hooks (.husky) label Feb 13, 2025
@novusnota novusnota added this to the v1.6.0 milestone Feb 13, 2025
@novusnota
Copy link
Member Author

novusnota commented Feb 13, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: ci Continuous Integration: GitHub Actions (.github), commit/push hooks (.husky)
Projects
None yet
Development

No branches or pull requests

1 participant