actions/msvc-dev-cmd
1
0
Fork 0
mirror of https://github.com/ilammy/msvc-dev-cmd.git synced 2026-09-07 06:07:19 +08:00
Code Issues Packages Projects Releases Wiki Activity
40 Commits 6 Branches 19 Tags
v1.6.0
Commit Graph

10 Commits

Author SHA1 Message Date
Alexei Lozovsky 6f493f9a67 Architecture aliases: Win32 & Win64 (#29) 
By a public request, let's support aliases for architecture parameters.
Treat "arch: Win32" as "x86" and "Win64" as "x64".

Test this on CI just in case x86 breaks or something.
 2021-03-07 08:23:48 +02:00
Ewout ter Hoeven aa2e60900e CI: Cleanup, checkout v2 (#24) 
- Remove the fail-fast: tag, it's non-functional since a matrix isn't used anymore
- Update to the faster checkout v2
 2021-02-01 14:01:31 +02:00
ilammy ddf4cb029f Fail audit on moderate and above vulnerabilities 
Set the threshold to "moderate" and above. Currently msvc-dev-cmd has
an issue in transitive dev-dependency "minimist" [1] via somewhat long
chain of dependencies:

  - eslint > file-entry-cache > flat-cache > write > mkdirp > minimist
  - eslint > mkdirp > minimist

In order for this to be resolved all these packages need to do something
about their pinned versions. I don't want to sit there with a red build
because of some possible low-severity prototype pollution in dev
dependency. Anything higher -- okay, I'll look at at, and apply a fix
if necessary. (Maybe we should not audit dev dependencies at all...)

This particular vulnerability can be exploited by an attacker who can
submit a pull request and do "something bad"™ to Actions runners
executing jobs for this repository. However, since it's a dev
dependency, nothing will happen to our users. So we can safely ignore
this advisory.

[1]: https://npmjs.com/advisories/1179
 2020-03-19 08:41:04 +02:00
ilammy 26cb400781 Run "npm audit" for release branch too 
I'd like to be notified about weird vulnerabilities in JavaScript
libraries for the release branch as well. It's double important
since the release branch ships particular pinned version of *all*
dependencies.
 2020-03-19 08:34:02 +02:00
ilammy aa189b6b13 Refresh dependencies 
It's not like we need any new features, but let's bump the versions
because we are in JavaScript land.

Also, run "npm audit" regularly, just in case a serious vulnerability
is discovered.
 2020-02-12 00:19:19 +02:00
ilammy 164e882247 Integration test for release version 
Make sure that the released version is also fine. Run this test every
time a push is made into the release branch as well as on schedule.
 2020-02-12 00:00:24 +02:00
ilammy a71277ef87 Use cmd.exe as shell 
It works well and we don't need PowerShell which has weird notion of
default executable search path.
 2020-02-12 00:00:24 +02:00
ilammy 987899132c Run test job at 06:00 every day 
Well, it seems the environment is changing so we'd better run the tests
reguarly to see whether something breaks in a timely manner.

GitHub Actions also don't offer other Windows environments now, only
windows-latest is available. Reduce test matrix to only that.
 2020-02-11 23:27:51 +02:00
ilammy d33b04e19c Verify configured environment 
Try compiling some C code, If it works then we're probably fine.
I don't even try to verify cross-compilation because I don't need it.
It should work, but that's not my problem right now.
 2019-10-02 00:53:54 +03:00
ilammy 3fdf9b2e34 Initial action stub 
Now that I know how to write some simple action, let's make a stub
more complete. For example, I already know what inputs I would like
to handle for this action.
 2019-10-01 22:15:47 +03:00