Since luvit's lit dependencies are included inline in the git repo, it's possible to patch them without publishing the changes to lit. But when you want to publish a new version of luvit to lit you need to publish any changed deps as well.

Make sure you're authenticated with your github username and online to the main lit database.

lit auth [your username]
lit up wss://lit.luvit.io/

Also make sure you have the latest lit. It must be at least 0.10.4, check with lit version.

Update the Makefile and make.bat with the latest lit version as well so that the CI servers and new users will have the same version you're using. Record the lit change in the CHANGELOG if it's updated.

To see what needs version bumping, run this from the luvit git tree:

lit add deps/*

This will attempt to add all the deps. It will sync with the upstream to pull down any new versions of packages not found in your local database. It will then import the packages from disk and try to sign and add them.

If a version already exists it will crash with a message telling you to bump the version. Once you're bumped to an appropriate version and recorded the changes to the changelog, repeat the step above to see what else was changed.

A sample changelog for the luvit release:

• [email protected]: Updated bundled lit version.
• [email protected]: Added more foobar power
• [email protected]: patches for security holes

Now let's update the package.lua file. Running lit install will warn for any version mismatches where the best version is newer than what's in the package.lua. It's best to update these at this time before bumping luvit's version.

Once that is all synced up, bump luvit's version in package.lua.

Don't forget to add a new entry in the CHANGELOG with the changes and the new luvit version.

Publish the new luvit to lit with:

lit publish deps/* .

(Note the . at the end)

Commit the version bump and create a signed annotated tag containing the changes for this version in it's body.

git tag -a -s 1.9.3

Push the branch and the tags to github.

git push
git push --tags

Celebrate the release! Announce on twitter, irc, workroom, etc.