matrix/matrix-js-sdk
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-js-sdk.git synced 2025-11-28 05:03:59 +03:00
Code Activity
7,707 Commits 238 Branches 514 Tags
24f9075a84d488ad76ac3d7279a31f940e24e09a
Commit Graph

73 Commits

Author SHA1 Message Date
Michael Telatynski
1f7e80c68d Require confirmation when doing proper release when intending to make an RC (#2540) 2022-07-27 09:12:57 +01:00
Michael Telatynski
9523978861 Update release.sh to support a staging branch (#2514) 2022-07-13 09:43:12 +01:00
Michael Telatynski
b2120a0a13 Initial attempt at automating jsdoc (#2382) 
* Initial attempt at automating jsdoc

* Commit tested jsdoc workflow
 2022-05-25 21:52:24 +01:00
David Baker
e4703989fe Add git archive learnings to release script comment (#2069) 2021-12-14 15:46:34 +00:00
David Baker
bfb2c5aad0 Fix release script to handle no signing ID 
We now use the file for stuff other than just the signing ID, so
the file may be present but with no signing ID: handle this case.
 2021-08-16 14:38:42 +01:00
David Baker
08821e499c Switch to new changelog generator 2021-08-03 17:51:42 +01:00
Germain Souquet
f0ae9b0100 Do not generate a lockfile when running in CI 2021-07-07 16:11:14 +02:00
J. Ryan Stinnett
c410954bad Replace dot-json with jq equivalents 2020-12-22 13:39:42 +00:00
J. Ryan Stinnett
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
J. Ryan Stinnett
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
J. Ryan Stinnett
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
J. Ryan Stinnett
f9f345e428 Move cache clean above install 2020-10-20 11:42:28 +01:00
J. Ryan Stinnett
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
Michael Telatynski
cfe90dbed5 Always push docs if they are generated 2020-09-24 12:47:23 +01:00
J. Ryan Stinnett
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
J. Ryan Stinnett
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
J. Ryan Stinnett
26e9dfb4fb Add latest dist-tag for a release 2020-02-26 14:07:20 +00:00
J. Ryan Stinnett
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
J. Ryan Stinnett
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
Travis Ralston
ccca6f4b6d Re-add dist script usage to js-sdk and release script 2020-01-14 14:44:06 -07:00
Travis Ralston
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
J. Ryan Stinnett
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
David Baker
821f1c876b Undo unintentional commenting 2019-04-30 11:48:38 +01:00
David Baker
f5cbdeac8f Trigger react-sdk build in buildkite pipeline 2019-04-26 18:06:04 +01:00
David Baker
6920dfb800 Yarn needs --new-version to create a new version 2019-03-13 14:23:51 +00:00
J. Ryan Stinnett
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
J. Ryan Stinnett
073a025b83 Try again to commit package-lock.json 2019-02-14 14:20:31 +00:00
David Baker
bd3d26422d git st is not a standard thing 2019-02-13 18:20:16 +00:00
David Baker
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
Bruno Windels
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
Bruno Windels
0a88d419c6 allow non-ff merge from release branch into master 2018-10-01 17:21:01 +02:00
Bruno Windels
55ca03f100 make release compatible with latest release of hub (2.5) 2018-09-28 12:51:31 +02:00
Bruno Windels
83708725b2 check youre logged in with correct npm user when releasing 2018-09-28 11:16:00 +02:00
Bruno Windels
e8e1b431ad make usage of hub compatible with latest version (2.5) 2018-09-27 11:28:01 +01:00
Matthew Hodgson
f6622e0bcd unbreak riot-web release process 2017-06-01 02:41:47 +01:00
Richard van der Hoff
672ad68c64 release.sh: download the tarball from git to verify it 2017-05-18 18:58:50 +01:00
David Baker
4523ae7d29 Checkout release branch *before* exiting script 2017-04-10 16:15:06 +01:00
David Baker
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
David Baker
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
David Baker
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
Richard van der Hoff
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
Richard van der Hoff
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
Kegan Dougal
df7ac77113 Review comments 2017-01-04 13:57:51 +00:00
Kegan Dougal
1b222249c4 Reset ret before reusing it 2017-01-04 11:56:01 +00:00
Kegan Dougal
126967cb90 release.sh: Bail early if there are uncommitted changes 2017-01-04 11:47:33 +00:00
Kegan Dougal
05cbc217a0 Add more docs to explain how to do releases 2017-01-04 11:27:34 +00:00
Kegan Dougal
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
David Baker
456135a6ec get latest changes after updating changelog 2016-12-16 17:39:24 +00:00
David Baker
d3b63c592e Set GIT_COMITTER_EMAIL 
so the release tag verifies correctly
 2016-12-12 15:37:09 +00:00
David Baker
73e86bfc5d Don't depend on having a build_dir 
to get latest changes
 2016-12-09 20:17:25 +00:00