Skip to content

Things to do before Release #100

@JackRobards

Description

@JackRobards

Tracking issue for Changes to do before the initial Release.

  • Setup Publish Packages to NPM.
  • Setup Publish VSCode Extension.
  • Bump Major version of all packages.
  • Write a Status info document, explaining the fork and why this exists.

(Optional - some of these may be spun off into their own issue for after the first release)

  • Review Open PRs on parent lit-analyzer repo, and consider including some as part of this.
  • Set up more labels on the repo for issues.
  • Set up changesets

WIP Changelog for the release is below (a cleaner version of this can be found in the Releases, or individual CHANGELOG files).

Major changes in this fork (Breaking):

Minor changes in this fork:

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions