Conversation
38409b4 to
6c79509
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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
@_linked/cli@1.3.0
Minor Changes
3c81281Thanks @flyon! - Phase 0.3 accumulated changes:linked setup-publishcommand: scaffolds a changesets-based publish workflow in any package repo. Supports single-branch (default) and--dual-branch(main + dev with@nextprereleases). Patches package.json (publishConfig + changesets devDeps), generates package-lock.json in an isolated tmpdir, writes.github/workflows/{ci,publish,changeset-check}.yml, and optionally configures GitHub branch protection via--configure-github(usesghCLI).linked build-workspacenow invokes each package's ownyarn buildscript instead of the internal buildPackage pipeline. Lets @_linked/core use pure tsc, pure-CSS packages use no-ops, and lincd-style packages useyarn linked build.linked yarn(safeYarn) gainsLINKED_YARN_DRY_RUNenv for testing arg forwarding without executing..jsextensions but doesn't abort the build.npx tsconfig-to-dual-packageso the binary resolves from nearest node_modules.dependenciesfield.yarn linked buildpattern (matches foundational packages), Gruntfile removed.mrgit-template.json,yarn setupscript,linkedApp: trueflag,mrgitdevDep.linkedPackage: true/linkedApp: trueflags added to cli-methods readers (alongside legacylincd/lincdAppfor transition period).lincd-server/*imports in LincdServer.tsx migrated to@_linked/server/*.All notable changes to
@_linked/cli(formerlylincd-cli) are documented here.This project follows Keep a Changelog and Semantic Versioning.