This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
pushkin-cli@4.0.0
Major Changes
#290046ed03 Thanks @jessestorbeck! - The basic experiment template -- along with all other templates -- is now implemented as an npm package. The contents of the template remain unchanged, but are compressed into build/template.zip. pushkin-cli v4+ is required to install the new packaged templates.
The reason for this change has to do with Pushkin's transition to a monorepo structure. Previously, Pushkin distributed templates through each repo's GitHub releases, but the new monorepo made this more challenging (see #254). By moving to distributing all projects through npm, Pushkin is able to streamline both its deployment workflow and the CLI code itself.
#290ad84d51 Thanks @jessestorbeck! - The --nomigrations and --nocache flags in prep and start (respectively) are replaced with --no-migrations and --no-cache.
Minor Changes
#2907703288 Thanks @jessestorbeck! - Users can now delete and archive/unarchive experiments using the remove experiment (alias rm exp) command.
#290316d6ec Thanks @jessestorbeck! - Testing with Jest is set up by default on the user's site. Current tests distributed with experiment templates now work after installation.
#2852015e4a Thanks @jessestorbeck! - Fixed image tags in package READMEs so they display properly on npm
#2902421b20 Thanks @jessestorbeck! - If the user's site directory isn't empty when they call install site, the CLI now asks if they really want to install their site there.
@pushkin-templates/exp-basic@6.0.0
Major Changes
#290046ed03 Thanks @jessestorbeck! - The basic experiment template -- along with all other templates -- is now implemented as an npm package. The contents of the template remain unchanged, but are compressed into build/template.zip. pushkin-cli v4+ is required to install the new packaged templates.
The reason for this change has to do with Pushkin's transition to a monorepo structure. Previously, Pushkin distributed templates through each repo's GitHub releases, but the new monorepo made this more challenging (see #254). By moving to distributing all projects through npm, Pushkin is able to streamline both its deployment workflow and the CLI code itself.
Minor Changes
#290316d6ec Thanks @jessestorbeck! - Testing with Jest is set up by default on the user's site. Current tests distributed with experiment templates now work after installation.
#290838e225 Thanks @jessestorbeck! - Experiment templates are now implemented as npm packages. The contents of the templates remain essentially unchanged but are compressed into build/template.zip. pushkin-cli v4+ is required to install the new packaged templates.
The reason for this change has to do with Pushkin's transition to a monorepo structure. Previously, Pushkin distributed templates through each repo's GitHub releases, but the new monorepo made this more challenging (see #254). By moving to distributing all projects through npm, Pushkin is able to streamline both its deployment workflow and the CLI code itself.
Minor Changes
#290316d6ec Thanks @jessestorbeck! - Testing with Jest is set up by default on the user's site. Current tests distributed with experiment templates now work after installation.
@pushkin-templates/exp-lexical-decision@6.0.0
Major Changes
#290838e225 Thanks @jessestorbeck! - Experiment templates are now implemented as npm packages. The contents of the templates remain essentially unchanged but are compressed into build/template.zip. pushkin-cli v4+ is required to install the new packaged templates.
The reason for this change has to do with Pushkin's transition to a monorepo structure. Previously, Pushkin distributed templates through each repo's GitHub releases, but the new monorepo made this more challenging (see #254). By moving to distributing all projects through npm, Pushkin is able to streamline both its deployment workflow and the CLI code itself.
Minor Changes
#290316d6ec Thanks @jessestorbeck! - Testing with Jest is set up by default on the user's site. Current tests distributed with experiment templates now work after installation.
@pushkin-templates/exp-self-paced-reading@6.0.0
Major Changes
#290838e225 Thanks @jessestorbeck! - Experiment templates are now implemented as npm packages. The contents of the templates remain essentially unchanged but are compressed into build/template.zip. pushkin-cli v4+ is required to install the new packaged templates.
The reason for this change has to do with Pushkin's transition to a monorepo structure. Previously, Pushkin distributed templates through each repo's GitHub releases, but the new monorepo made this more challenging (see #254). By moving to distributing all projects through npm, Pushkin is able to streamline both its deployment workflow and the CLI code itself.
Minor Changes
#290316d6ec Thanks @jessestorbeck! - Testing with Jest is set up by default on the user's site. Current tests distributed with experiment templates now work after installation.
@pushkin-templates/site-basic@1.0.0
Major Changes
#290046ed03 Thanks @jessestorbeck! - The basic site template -- along with all other templates -- is now implemented as an npm package. The contents of the template remain unchanged, but are compressed into build/template.zip. pushkin-cli v4+ is required to install the new packaged template.
The reason for this change has to do with Pushkin's transition to a monorepo structure. Previously, Pushkin distributed templates through each repo's GitHub releases, but the new monorepo made this more challenging (see #254). By moving to distributing all projects through npm, Pushkin is able to streamline both its deployment workflow and the CLI code itself.
pushkin-api@1.6.1
Patch Changes
#2852015e4a Thanks @jessestorbeck! - Fixed image tags in package READMEs so they display properly on npm
pushkin-client@1.7.2
Patch Changes
#2852015e4a Thanks @jessestorbeck! - Fixed image tags in package READMEs so they display properly on npm
pushkin-worker@3.0.1
Patch Changes
#2852015e4a Thanks @jessestorbeck! - Fixed image tags in package READMEs so they display properly on npm
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
pushkin-cli@4.0.0
Major Changes
#290
046ed03
Thanks @jessestorbeck! - The basic experiment template -- along with all other templates -- is now implemented as an npm package. The contents of the template remain unchanged, but are compressed intobuild/template.zip
.pushkin-cli
v4+ is required to install the new packaged templates.The reason for this change has to do with Pushkin's transition to a monorepo structure. Previously, Pushkin distributed templates through each repo's GitHub releases, but the new monorepo made this more challenging (see #254). By moving to distributing all projects through npm, Pushkin is able to streamline both its deployment workflow and the CLI code itself.
#290
ad84d51
Thanks @jessestorbeck! - The--nomigrations
and--nocache
flags inprep
andstart
(respectively) are replaced with--no-migrations
and--no-cache
.Minor Changes
#290
7703288
Thanks @jessestorbeck! - Users can now delete and archive/unarchive experiments using theremove experiment
(aliasrm exp
) command.#290
316d6ec
Thanks @jessestorbeck! - Testing with Jest is set up by default on the user's site. Current tests distributed with experiment templates now work after installation.Patch Changes
#285
668abcb
Thanks @jessestorbeck! - Removed stray console.log#285
2015e4a
Thanks @jessestorbeck! - Fixed image tags in package READMEs so they display properly on npm#290
2421b20
Thanks @jessestorbeck! - If the user's site directory isn't empty when they callinstall site
, the CLI now asks if they really want to install their site there.@pushkin-templates/exp-basic@6.0.0
Major Changes
#290
046ed03
Thanks @jessestorbeck! - The basic experiment template -- along with all other templates -- is now implemented as an npm package. The contents of the template remain unchanged, but are compressed intobuild/template.zip
.pushkin-cli
v4+ is required to install the new packaged templates.The reason for this change has to do with Pushkin's transition to a monorepo structure. Previously, Pushkin distributed templates through each repo's GitHub releases, but the new monorepo made this more challenging (see #254). By moving to distributing all projects through npm, Pushkin is able to streamline both its deployment workflow and the CLI code itself.
Minor Changes
316d6ec
Thanks @jessestorbeck! - Testing with Jest is set up by default on the user's site. Current tests distributed with experiment templates now work after installation.@pushkin-templates/exp-grammaticality-judgment@6.0.0
Major Changes
#290
838e225
Thanks @jessestorbeck! - Experiment templates are now implemented as npm packages. The contents of the templates remain essentially unchanged but are compressed intobuild/template.zip
.pushkin-cli
v4+ is required to install the new packaged templates.The reason for this change has to do with Pushkin's transition to a monorepo structure. Previously, Pushkin distributed templates through each repo's GitHub releases, but the new monorepo made this more challenging (see #254). By moving to distributing all projects through npm, Pushkin is able to streamline both its deployment workflow and the CLI code itself.
Minor Changes
316d6ec
Thanks @jessestorbeck! - Testing with Jest is set up by default on the user's site. Current tests distributed with experiment templates now work after installation.@pushkin-templates/exp-lexical-decision@6.0.0
Major Changes
#290
838e225
Thanks @jessestorbeck! - Experiment templates are now implemented as npm packages. The contents of the templates remain essentially unchanged but are compressed intobuild/template.zip
.pushkin-cli
v4+ is required to install the new packaged templates.The reason for this change has to do with Pushkin's transition to a monorepo structure. Previously, Pushkin distributed templates through each repo's GitHub releases, but the new monorepo made this more challenging (see #254). By moving to distributing all projects through npm, Pushkin is able to streamline both its deployment workflow and the CLI code itself.
Minor Changes
316d6ec
Thanks @jessestorbeck! - Testing with Jest is set up by default on the user's site. Current tests distributed with experiment templates now work after installation.@pushkin-templates/exp-self-paced-reading@6.0.0
Major Changes
#290
838e225
Thanks @jessestorbeck! - Experiment templates are now implemented as npm packages. The contents of the templates remain essentially unchanged but are compressed intobuild/template.zip
.pushkin-cli
v4+ is required to install the new packaged templates.The reason for this change has to do with Pushkin's transition to a monorepo structure. Previously, Pushkin distributed templates through each repo's GitHub releases, but the new monorepo made this more challenging (see #254). By moving to distributing all projects through npm, Pushkin is able to streamline both its deployment workflow and the CLI code itself.
Minor Changes
316d6ec
Thanks @jessestorbeck! - Testing with Jest is set up by default on the user's site. Current tests distributed with experiment templates now work after installation.@pushkin-templates/site-basic@1.0.0
Major Changes
#290
046ed03
Thanks @jessestorbeck! - The basic site template -- along with all other templates -- is now implemented as an npm package. The contents of the template remain unchanged, but are compressed intobuild/template.zip
.pushkin-cli
v4+ is required to install the new packaged template.The reason for this change has to do with Pushkin's transition to a monorepo structure. Previously, Pushkin distributed templates through each repo's GitHub releases, but the new monorepo made this more challenging (see #254). By moving to distributing all projects through npm, Pushkin is able to streamline both its deployment workflow and the CLI code itself.
pushkin-api@1.6.1
Patch Changes
2015e4a
Thanks @jessestorbeck! - Fixed image tags in package READMEs so they display properly on npmpushkin-client@1.7.2
Patch Changes
2015e4a
Thanks @jessestorbeck! - Fixed image tags in package READMEs so they display properly on npmpushkin-worker@3.0.1
Patch Changes
2015e4a
Thanks @jessestorbeck! - Fixed image tags in package READMEs so they display properly on npm