Added another manual bootstrap example - #1
Open
rpanjwani wants to merge 6210 commits into
Open
Conversation
petebacondarwin
force-pushed
the
master
branch
from
September 16, 2014 11:25
02dc2aa to
fd2d6c0
Compare
jeffbcross
force-pushed
the
master
branch
2 times, most recently
from
October 2, 2014 22:08
cad9560 to
f294244
Compare
jeffbcross
force-pushed
the
master
branch
4 times, most recently
from
October 10, 2014 17:37
e8dc429 to
e83fab9
Compare
petebacondarwin
force-pushed
the
master
branch
from
October 19, 2014 10:57
4dd5a20 to
998c61c
Compare
petebacondarwin
force-pushed
the
master
branch
from
December 24, 2014 13:15
49bb367 to
3e42b22
Compare
petebacondarwin
force-pushed
the
master
branch
2 times, most recently
from
February 7, 2015 10:26
afe61a5 to
9d53e5a
Compare
pkozlowski-opensource
force-pushed
the
master
branch
from
February 28, 2015 12:30
cc17b1b to
7cfa79e
Compare
matsko
force-pushed
the
master
branch
2 times, most recently
from
August 19, 2015 17:40
eaa6ad7 to
dc48aad
Compare
petebacondarwin
force-pushed
the
master
branch
from
September 22, 2015 09:43
6571d7a to
e1f4f23
Compare
Previously, we only deployed the built files to Google Cloud Storage for the `code-angularjs-org` Firebase project. This meant that the other Firebase services (such as functions, hosting, storage) were not updated when we made changes to their source code or configuration. (This isn't a problem at the moment, since the code/configuration for these service changes infrequently, but could bite us in the future.) This commit fixes this by ensuring that we deploy to all enabled Firebase services (currently functions, hosting and storage).
Previously, when deploying `scripts/{code,docs}.angularjs.org-firebase/`
to Firebase, we explicitly specified the target projects. Since the
project IDs are also specified in the respective `.firebaserc` files,
this was unnecessary (and meant we had multiple places to update if the
IDs changed).
This commit simplifies the process by automatically targeting the
default projects (as configured in the `.firebaserc` files) when
deploying to Firebase in CI.
This commit updates `firebase-admin`, `firebase-functions` and `firebase-tools` to latest versions to take advantage of the most recent fixes and improvements.
…sendStoredFile()`
Previously, the `sendStoredFile()` Firebase function used `.split('/')`
to split the request path into segments and later used `path.join()` to
join them back together. This worked fine on *nix based systems, which
use `/` as the path separator. On Windows, however, where `\` is the
path separator, the re-constructed paths could not be retrieved from the
Google Cloud Storage bucket. This prevented the Firebase emulators from
working correctly when testing the function locally on Windows.
This commit fixes the issue by using `.join('/')` to join the path
segments back together.
Closes #17114
In #17114, the `deploy-code` CI job was modified to also run some commands via `yarn`. It turns out that this breaks on CI, because the `deploy-code` job uses the `cloud-sdk` executor that does not have `yarn` installed. ([Example failure][1]) This commit fixes this by splitting the `deploy-code` job into two jobs: - `deploy-code-files` uses the `cloud-sdk` and uploads the files to Google Cloud. (This is essentially the `deploy-code` job from before #17114.) - `deploy-code-firebase` uses the `default` executor (which has `yarn` installed) and deploys to Firebase. (This essentially includes the new bits added in #17114.) [1]: https://circleci.com/gh/angular/angular.js/2712
Previously, the `deploy-code-firebase` CI job was run on any build corresponding to a git tag, the master branch or the stable branch. Given that all runs of `deploy-code-firebase` deploy to the same Firebase project (and overwrites previous deployments), there is no point in deploying from multiple branches/tags. This commit fixes this by ensuring that we only run the `deploy-code-firebase` job on builds for the master branch, which contains the most up-to-date code/configuration.
Bumps [ini](https://github.com/isaacs/ini) from 1.3.4 to 1.3.7. - [Release notes](https://github.com/isaacs/ini/releases) - [Commits](npm/ini@v1.3.4...v1.3.7) Signed-off-by: dependabot[bot] <support@github.com> Closes #17099
Bumps [https-proxy-agent](https://github.com/TooTallNate/node-https-proxy-agent) from 2.2.1 to 2.2.4. - [Release notes](https://github.com/TooTallNate/node-https-proxy-agent/releases) - [Commits](TooTallNate/proxy-agents@2.2.1...2.2.4) Signed-off-by: dependabot[bot] <support@github.com> Closes #17115
Bumps [bl](https://github.com/rvagg/bl) from 1.2.2 to 1.2.3. - [Release notes](https://github.com/rvagg/bl/releases) - [Commits](rvagg/bl@v1.2.2...v1.2.3) Signed-off-by: dependabot[bot] <support@github.com> Closes #17116
Bumps [elliptic](https://github.com/indutny/elliptic) from 6.5.3 to 6.5.4. - [Release notes](https://github.com/indutny/elliptic/releases) - [Commits](indutny/elliptic@v6.5.3...v6.5.4) Signed-off-by: dependabot[bot] <support@github.com> Closes #17119
assigment -> assignment Closes #17120
Bumps [y18n](https://github.com/yargs/y18n) from 3.2.1 to 3.2.2. - [Release notes](https://github.com/yargs/y18n/releases) - [Changelog](https://github.com/yargs/y18n/blob/master/CHANGELOG.md) - [Commits](https://github.com/yargs/y18n/commits) Signed-off-by: dependabot[bot] <support@github.com> Closes #17122
Propogate -> Propagate
- the subdomain was switched to a path many months ago - the angularjs.xlts.dev site will soon be used for hosting something else and the redirect removed (ASAP) Closes #17136
- from:483 vulnerabilities found - 273 Low | 38 Moderate | 168 High | 4 Critical - to: 389 vulnerabilities found - 259 Low | 28 Moderate | 98 High | 4 Critical Closes #17139
- update firebase scripts - from: 6 vulnerabilities found - Severity: 6 High - to: 0 vulnerabilities found Closes #17140
Bumps [normalize-url](https://github.com/sindresorhus/normalize-url) from 4.5.0 to 4.5.1. - [Release notes](https://github.com/sindresorhus/normalize-url/releases) - [Commits](https://github.com/sindresorhus/normalize-url/commits) Closes #17145
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 3.5.5 to 3.14.1. - [Release notes](https://github.com/nodeca/js-yaml/releases) - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@3.5.5...3.14.1) Closes #17147
Add a wiki link to MVC in case people have not heard of it before and want to read about it more. Closes #17152
Since version 93, Firefox started more closely following the spec on formatting `datetime-local` input values by removing trailing zeros from the string representation of the value. This causes some of our tests to fail ([example failure][1]). For example, a value is reported by Firefox as `2009-01-06T16:25` while the tests expect `2009-01-06T16:25:00.000`. I.e. Firefox started leaving out seconds/milliseconds if they are zero. According to [MDN][2], this is the correct behavior according to the spec. Indeed the spec says that [if the value of the element is a valid local date and time string, then it must be set to a **valid normalized local date and time string**][3], where **valid normalized local date and time string** is [defined as consisting of][4]: > - A valid date string representing the date. > - A U+0054 LATIN CAPITAL LETTER T character (T). > - A valid time string representing the time, expressed as the > **shortest possible string** for the given time (e.g. **omitting the > seconds component** entirely if the given time is zero seconds past > the minute). This commit fixes the relevant tests by explicitly specifying non-zero values for seconds and milliseconds. [1]: https://circleci.com/gh/angular/angular.js/3527 [2]: https://developer.mozilla.org/en-US/docs/Web/HTML/Date_and_time_formats #local_date_and_time_strings [3]: https://html.spec.whatwg.org/multipage/input.html #local-date-and-time-state-(type=datetime-local) [4]: https://html.spec.whatwg.org/multipage/common-microsyntaxes.html #concept-datetime-local Co-authored-by: George Kalpakas <kalpakas.g@gmail.com>
Previously, the `angularInit()` tests assumed that the Safari browser uses the `safari-extension:` protocol for browser extension URLs. This is true for versions <15. However, since v15, Safari on iOS only recognizes the `chrome-extension:` protocol, which causes the tests to fail ([example failure][1]). This commit updates the tests to use the correct protocol according to the version of Safari used. NOTE: On macOS, Safari v15+ recognizes both `safari-extension:` and `chrome-extension:`, so it is OK to always use the later with Safari v15+ (regardless of the platform). [1]: https://circleci.com/gh/angular/angular.js/3527 Co-authored-by: George Kalpakas <kalpakas.g@gmail.com> Closes #17166
* Docs homepage * Docs banner * Security and support pages * GitHub README * CHANGELOG
We're doing this final release to update poackage README files for npm.
Co-authored-by: Mike Brocchi <brocco@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
15 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added a manual bootstrap example in the bootstrap doc that deals with having multiple apps on the same page.