c410954bad
Replace dot-json with jq equivalents
2020-12-22 13:39:42 +00:00
1c7f95c0ee
Use TypeScript source for development, swap to build during release
...
This changes the JS SDK to point `main` to TypeScript source and remove any
indication of `typings`. For local development and CI workflows, it means many
steps can run without building first, which saves lots of time.
During release, we still build for Node and browsers as before. The release
script adjusts the `main` and `typings` fields before publishing and
distribution to point to the built output for those that use them.
2020-12-22 11:48:57 +00:00
9db0fe0795
Merge pull request #1518 from matrix-org/jryans/release-install-first
...
Install deps first as part of release
2020-10-20 15:45:25 +01:00
a8693d9d68
Skip editor prompts for merges
...
The merges are never edited, and even with this change they will still abort if
there are conflicts.
2020-10-20 11:47:59 +01:00
f9f345e428
Move cache clean above install
2020-10-20 11:42:28 +01:00
e678706414
Install deps first as part of release
...
This ensures we always install (without running build scripts) as the first step
of release process, as otherwise it may fail later due to mismatched types or
any number of other errors.
2020-10-20 11:20:57 +01:00
cfe90dbed5
Always push docs if they are generated
2020-09-24 12:47:23 +01:00
a9c9ec3977
Replace Riot with Element in docs and comments
...
This only covers the simple cases of references to issues and repos. More
complex areas, such as deployment scripts, will be handled separately.
Part of https://github.com/vector-im/element-web/issues/14864
2020-08-03 18:32:52 +01:00
629490c4ae
Adapt release script for riot-desktop
...
This allows the bulk of the release script to be used for riot-desktop, while
skipping the NPM and develop branch parts that do not apply.
Part of https://github.com/vector-im/riot-web/issues/13176
2020-04-15 18:10:46 +01:00
26e9dfb4fb
Add latest dist-tag for a release
2020-02-26 14:07:20 +00:00
f27d03a6bc
Always publish to next tag
...
This ensures that anyone who wants the latest version (pre-release or final
release) can always use the `next` tag.
2020-02-26 13:55:46 +00:00
15c2e4bb07
Publish pre-releases as a separate tag on npm
...
npm will install the newest version a package has published to the `latest` tag,
including pre-releases, which is not ideal since those may not be ready for
production use yet.
This uses an alternate tag (`next` is a common convention, but it can be
anything) for pre-releases so the default installs only get stable versions.
Fixes https://github.com/vector-im/riot-web/issues/12029
2020-01-27 20:40:35 +00:00
ccca6f4b6d
Re-add dist script usage to js-sdk and release script
2020-01-14 14:44:06 -07:00
601cefe975
Fix the release script for new build process
...
It doesn't seem to care what the version is, so just build the SDK normally.
2019-12-12 10:25:19 -07:00
0808c0edf1
Clean Yarn cache during release
...
Always run `yarn cache clean` during the `dist` step to workaround a Yarn bug
with Git commit package dependencies.
2019-09-26 11:18:20 +01:00
821f1c876b
Undo unintentional commenting
2019-04-30 11:48:38 +01:00
f5cbdeac8f
Trigger react-sdk build in buildkite pipeline
2019-04-26 18:06:04 +01:00
6920dfb800
Yarn needs --new-version to create a new version
2019-03-13 14:23:51 +00:00
2144791d52
Update scripts and docs to use yarn where appropriate
...
Most `npm` operations are replaced with `yarn`, which generally has better
behavior. However, steps like publish that write to the NPM registry are left to
`npm`, which currently handles these tasks best.
2019-03-08 15:45:57 +00:00
073a025b83
Try again to commit package-lock.json
2019-02-14 14:20:31 +00:00
bd3d26422d
git st is not a standard thing
2019-02-13 18:20:16 +00:00
68c8fe0fa9
Release script: commit package-lock.json
...
Commit the package-lock.json when bumping the version, otherwise
the versions get out of sync, and this is going to matter more now
that jenkins runs `npm ci` which is fussy about these things.
2019-02-13 13:40:46 +00:00
2d3669b03b
Merge pull request #749 from matrix-org/bwindels/releaseimprovements
...
Extra checks to avoid release script blowing up mid-process.
2018-12-12 09:07:12 +00:00
0a88d419c6
allow non-ff merge from release branch into master
2018-10-01 17:21:01 +02:00
55ca03f100
make release compatible with latest release of hub (2.5)
2018-09-28 12:51:31 +02:00
83708725b2
check youre logged in with correct npm user when releasing
2018-09-28 11:16:00 +02:00
e8e1b431ad
make usage of hub compatible with latest version (2.5)
2018-09-27 11:28:01 +01:00
f6622e0bcd
unbreak riot-web release process
2017-06-01 02:41:47 +01:00
672ad68c64
release.sh: download the tarball from git to verify it
2017-05-18 18:58:50 +01:00
4523ae7d29
Checkout release branch *before* exiting script
2017-04-10 16:15:06 +01:00
19e5eda773
Don't leave the gh-pages branch checked out
...
After a pre-release, check out the release branch again rather
than leaving the working copy on the gh-pages branch
2017-04-10 15:52:37 +01:00
e63c660162
Fix release script
...
Publish to npm before switching to the doc branch: previously we
published from master, but since we now now longer merge
pre-releases to master, publish from the release branch (just
not the doc branch because that won't work).
2017-04-07 16:55:38 +01:00
4388cc207f
Merge pull request #351 from matrix-org/rav/sign_source_tarball
...
Make a sig for source tarballs when releasing
2017-02-06 11:32:45 +01:00
3d9173a877
Make a sig for source tarballs when releasing
...
When we are doing a signed release, also create a sig for the 'archive' tarball
which github creates for us.
Fixes https://github.com/vector-im/riot-web/issues/3024 .
2017-02-04 11:10:40 +00:00
cb88f53587
When doing a pre-release, don't bother merging to master and develop.
...
This assumes that we'll eventually do a proper release (or merge the prerel
manually), and saves twiddling the package.json on downstream projects for each
prerelease.
2017-02-04 11:07:14 +00:00
df7ac77113
Review comments
2017-01-04 13:57:51 +00:00
1b222249c4
Reset ret before reusing it
2017-01-04 11:56:01 +00:00
126967cb90
release.sh: Bail early if there are uncommitted changes
2017-01-04 11:47:33 +00:00
05cbc217a0
Add more docs to explain how to do releases
2017-01-04 11:27:34 +00:00
d6e4d0a417
Remove RELEASING.md
...
vdh says it is out of date and is misleading and should be removed, so removing it.
2017-01-04 11:16:59 +00:00
456135a6ec
get latest changes after updating changelog
2016-12-16 17:39:24 +00:00
d3b63c592e
Set GIT_COMITTER_EMAIL
...
so the release tag verifies correctly
2016-12-12 15:37:09 +00:00
73e86bfc5d
Don't depend on having a build_dir
...
to get latest changes
2016-12-09 20:17:25 +00:00
67e75fb7af
Invoke changelog_head from outside the pushd
...
so we know the relative path is right
2016-12-09 19:19:40 +00:00
5ce5299651
Update release script to do signed releases
...
if a signing ID is set in release_config.yaml
Also set the release text to the relevant changelog entry
2016-12-09 17:04:19 +00:00
d8de23228f
actually speak valid git in release.sh
2016-11-19 01:51:19 +02:00
579218aafc
correctly crash out if jq or hub are missing
2016-11-19 01:25:36 +02:00
47e12fcc3e
Use env var for dist version
...
Don't pass it as an arg because that really confuses npm scripts
that aren;t expecting an arg (npm it just blindly appends it).
2016-11-04 09:42:08 +00:00
dcb987732c
Add version arg to the dist script
...
as per comment
2016-11-02 11:36:53 +00:00
01593d1a69
Set the release branch variable
...
when using the current branch, otherwise we'll try to check out
the wrong thing
2016-11-02 10:25:47 +00:00
J. Ryan Stinnett