Didn't we mark that as a known issue? Anyway, thanks for the reminder about bumping version to align with npm. I'll read the rest of it later. I did make some changes to the npm release script, in the last release I think, so it might not be an issue this time, but I agree we need to look out for it and add some manual checks. Hopefully somebody else can step up to be the RM this time, but I'll be there to help with whatever.
________________________________ From: Josh Tynjala <joshtynj...@bowlerhat.dev> Sent: Tuesday, March 12, 2024 7:47 PM To: dev@royale.apache.org <dev@royale.apache.org> Subject: Re: New Release? Just a reminder: the npm version of Royale is currently one ahead of where it should be: 0.9.11 instead of 0.9.10. With that in mind, we probably need the new Royale release to be version 0.9.12. This has happened a couple of times now. We also had one npm release that was missing most of its files, so it didn't work at all. It's okay. Mistakes happen. If the release manager instructions don't warn about potential issues around the npm release, though, I think that we should update them to include some extra manual checks before publishing to npm. Here are some things that might be worth mentioning (perhaps with some editing): The `npm pack` command creates a .tgz bundle of the package. You can extract this with your favorite program to manually check what's inside. Side note: The .tgz file can also be passed to `npm install` to test installation. It works something like this: npm install -g royale-js.tgz npm install -g royale-js-swf.tgz --foreground-scripts While `npm publish` with no arguments can be run in the repo directory that contains package.json, you can also pass the .tgz bundle created by `npm pack` to `npm publish`. If you've already checked the contents of the .tgz bundle, then it makes sense to submit that directly. npm publish royale-js.tgz Finally, `npm publish` has an optional --dry-run command line option that will fake a submission locally. The output from this command will include the version and a list of all included files. It will stop before submitting to the registry, though. On Tue, Mar 12, 2024 at 9:30 AM Yishay Weiss <yishayj...@hotmail.com> wrote: > Hi Guys, > > It's been a while since we've done a release. There have been some recent > compiler changes and some minor asjs fixes, which together might warrant > one. Thougths on this? Is anybody planning any big changes soon? > > Thanks, > Yishay >