Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add automated publishing of weekly alpha releases to NPM #19441

Merged
merged 1 commit into from
Mar 1, 2021

Commits on Mar 1, 2021

  1. Add automated publishing of weekly alpha releases to NPM

    By default the ember-cli blueprint uses ember-try to download the `npm
    pack` result of the most recent caanry build from Amazon S3 (this is
    usually setup to run in that addon's CI configuration). Unfortunately,
    some organizations have security restrictions **preventing** access to
    the internet during CI jobs. They often have customized NPM mirrors that
    do work (otherwise how would they ever build / test JS code), but block
    access to the rest of the internet. Up until this change, those
    organizations simply **could not** be early testers of our canary
    builds.
    
    This change adds a new CI job to auto-publish a new `-alpha.x` release
    to NPM once a week (on Mondays). This will allow folks to leverage their
    normal `npm install` infrastructure to be able to test canary Ember
    builds once a week (though we could in theory decide to make more
    publish). However, since the process is automated these alphas will not
    include changelog entries. It is theoretically possible that we would
    prefer to leverage this infrastructure for testing addons against
    published tags (instead of using `ember-source-channel-url`), but that
    would reduce our speed of identifiying regressions.
    rwjblue committed Mar 1, 2021
    Configuration menu
    Copy the full SHA
    0079b11 View commit details
    Browse the repository at this point in the history