Page MenuHomePhabricator

[native] Script to bump native version
ClosedPublic

Authored by ashoat on Thu, Mar 20, 7:24 PM.
Tags
None
Referenced Files
F5100062: D14486.diff
Mon, Mar 31, 10:25 AM
F5093876: D14486.id47511.diff
Sun, Mar 30, 1:51 PM
Unknown Object (File)
Sun, Mar 30, 11:02 AM
Unknown Object (File)
Sun, Mar 30, 9:32 AM
Unknown Object (File)
Sun, Mar 30, 3:28 AM
Unknown Object (File)
Sat, Mar 29, 7:06 PM
Unknown Object (File)
Sat, Mar 29, 9:01 AM
Unknown Object (File)
Sat, Mar 29, 7:25 AM
Subscribers
None

Details

Summary

Claude helped generate this. Will save me some time during release processes.

Test Plan

Ran the script and it worked!

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Accidentally had bumped version in version.js

Harbormaster returned this revision to the author for changes because remote builds failed.Thu, Mar 20, 7:45 PM
Harbormaster failed remote builds in B33804: Diff 47514!

Avoid setting type: "module" in native/package.json as it breaks some scripts

Harbormaster returned this revision to the author for changes because remote builds failed.Thu, Mar 20, 8:30 PM
Harbormaster failed remote builds in B33805: Diff 47515!

Add .mjs files to .flowconfig

Harbormaster returned this revision to the author for changes because remote builds failed.Thu, Mar 20, 8:56 PM
Harbormaster failed remote builds in B33806: Diff 47516!
native/scripts/update-mobile-version.mjs
5 ↗(On Diff #47516)

LGTM, but:

  • don't we need to document it somewhere in some README?
  • as far as I understand to update the version you bump the version in version.mjs first, then run the script, can't we automate the first step too?
  • you can also automate making commits too later?
This revision is now accepted and ready to land.Fri, Mar 21, 12:32 AM
  • don't we need to document it somewhere in some README?

No, I don't think so. We don't really document the release process in the README.

  • as far as I understand to update the version you bump the version in version.mjs first, then run the script, can't we automate the first step too?

Yeah, and I think this could be done for keyserver and web too. But I'm starting with this script because it's currently the most annoying / rote part of the process for me. Hope to make further improvements at a later point.

  • you can also automate making commits too later?

Yeah agree we could improve the process further.

This revision was automatically updated to reflect the committed changes.