aboutsummaryrefslogtreecommitdiffstats
path: root/community/nodejs-current
Commit message (Collapse)AuthorAgeFilesLines
* community/nodejs-current: upgrade to 9.10.0Trevor2018-03-301-2/+2
|
* community/nodejs-current: upgrade to 9.8.0Jakub Jirutka2018-03-171-2/+2
|
* community/nodejs-current: upgrade to 9.7.1Jakub Jirutka2018-03-041-2/+2
|
* community/nodejs-current: upgrade to 9.7.0Jakub Jirutka2018-03-021-2/+2
|
* community/nodejs-current: upgrade to 9.5.0Jakub Jirutka2018-02-091-2/+2
|
* community/nodejs-current: upgrade to 9.4.0Remi Caumette2018-02-051-2/+2
|
* community/nodejs-current: upgrade to 9.3.0Jakub Jirutka2017-12-311-2/+2
|
* community/nodejs-current: upgrade to 9.2.1Jakub Jirutka2017-12-091-2/+8
| | | | | | | See: https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/ CVE-2017-3738 does not affect our package, because we don't use bundled OpenSSL library. I'm not sure about CVE-2017-15896.
* community/nodejs-current: Update to 9.2.0Trevor2017-11-281-2/+2
| | | This adds the pkgver and sha512sum for nodejs-v9.2.0
* community/*: fix homepage url and source from http:// to https://Jakub Jirutka2017-11-191-1/+1
| | | | | | | Most of these updates is based on data from https://repology.org/, detection based on permanent redirect from http:// to https://. $source urls are updated when they contain $url as substring.
* community/nodejs-current: upgrade to 9.1.0Tim Brust2017-11-081-2/+2
|
* community/nodejs-current: remove -npm subpackageJakub Jirutka2017-10-311-18/+4
| | | | | | npm is a separate project, it's just bundled with nodejs, so it doesn't make much sense to provide two npm versions. Eventually I'll move npm into a separate package.
* community/nodejs-current: upgrade to 9.0.0Jakub Jirutka2017-10-311-2/+2
|
* community/nodejs-current: upgrade to 8.7.0Jakub Jirutka2017-10-172-38/+4
|
* community/nodejs-current: upgrade to 8.6.0Jakub Jirutka2017-10-031-2/+2
|
* nodejs-current: add basic checkJakub Jirutka2017-09-231-1/+13
|
* community/nodejs-current: modernize abuildJakub Jirutka2017-09-231-12/+11
|
* community/nodejs-current: upgrade to 8.5.0Jakub Jirutka2017-09-231-2/+2
|
* community/nodejs-current: upgrade to 8.4.0Ole-Martin Bratteng2017-08-251-2/+2
|
* community/nodejs-current: upgrade to 8.3.0Ole-Martin Bratteng2017-08-151-2/+2
|
* community/nodejs-current: upgrade to 8.2.1Ole-Martin Bratteng2017-07-211-2/+2
|
* community/nodejs-current: upgrade to 8.1.4Ole-Martin Bratteng2017-07-141-3/+3
|
* community/nodejs-current: build with system c-aresNatanael Copa2017-07-141-2/+3
|
* community/nodejs-current: upgrade to 8.1.3Ole-Martin Bratteng2017-06-301-2/+2
|
* community/nodejs-current: upgrade to 8.1.2Ole-Martin Bratteng2017-06-271-2/+2
|
* community/nodejs-current: fix checksumNatanael Copa2017-06-051-1/+1
|
* community/nodejs-current: upgrade to 8.0.0Ole-Martin Bratteng2017-06-021-2/+2
|
* community/nodejs-current: upgrade to 7.10.0Ole-Martin Bratteng2017-05-111-2/+2
|
* community/nodejs-current: update ppc patch to fit samplerGustavo Romero2017-04-132-4/+4
| | | | | | | | Update ppc patch due to a refactor in sampler.cc internals introduced in [1] where 'state' variable is now treated as a pointer. [1] https://goo.gl/YwyjCC
* community/nodejs-current: upgrade to 7.9.0Martin Bratteng2017-04-121-2/+2
|
* community/nodejs-current: upgrade to 7.8.0Martin Bratteng2017-03-301-2/+2
|
* community/nodejs-current: fix compilation on PPC with muslJakub Jirutka2017-03-282-2/+36
| | | | Port @gromero's patch from main/nodejs.
* community/nodejs-current: upgrade to 7.7.4Martin Bratteng2017-03-231-2/+2
|
* community/nodejs-current: upgrade to 7.7.3Martin Bratteng2017-03-201-2/+2
|
* community/nodejs-current: upgrade to 7.7.2Ole-Martin Bratteng2017-03-121-3/+3
|
* community/nodejs-current: move npm to subpackageEd Robinson2017-03-071-2/+15
|
* community/nodejs-current: update to v7.7.1Jose-Luis Rivas2017-03-031-2/+2
|
* community/nodejs-current: update to v7.6.0Jose-Luis Rivas2017-02-271-6/+2
|
* community/nodejs-current: fix indentationJakub Jirutka2017-02-251-1/+1
|
* community/nodejs-current: upgrade to v7.5.0Jose-Luis Rivas2017-02-092-75/+6
| | | | | | No need for the use-system-ca-certs.patch since it's already merged into upstream. Removing the bundled certs from source makes it unbuildable and there's no need to remove it from source.
* community/nodejs-current: add provides=nodejsEd Robinson2017-01-311-1/+2
| | | | In order that yarn can be used with either version of nodejs.
* community/nodejs-current: add depends ca-certificatesJakub Jirutka2017-01-141-1/+2
|
* community/nodejs-current: upgrade to 7.2.1Jakub Jirutka2016-12-131-4/+4
|
* main/nodejs: rename to nodejs-current and move to communityJakub Jirutka2016-11-273-0/+153
Odd-numbered versions, like this one (v7), are supported by upstream only for 9 months. When a new odd-numbered major release is cut, the previous even-numbered major version transitions to the Long Term Support plan (LTS). Packages in Alpine stable must be supported for 2 years, so we should keep only LTS version in the stable. Therefore this package is renamed to nodejs-current and moved to the community repository. The nodejs-lts package is going to be renamed to nodejs. See https://github.com/nodejs/LTS#lts-schedule
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-12 00:02:27 +0000