David Glasser
4daaa76b12
METEOR@1.0.4
2015-03-17 13:06:07 -07:00
David Glasser
af0469da35
Bump other packages to -rc.0
2015-03-05 22:54:07 -08:00
Slava Kim
27f249bfed
A lot of crazy package bumps
2015-01-21 14:03:55 -08:00
David Glasser
6b204ca73a
Bump package versions for 1.0.2
2014-12-19 10:31:59 -08:00
David Glasser
73b809c122
Bump versions for 1.0.2.
2014-12-11 22:44:41 -08:00
David Glasser
6ea8443f30
Update calls to addFiles, onUse, and onTest
2014-12-09 20:18:31 -08:00
David Glasser
de5f68cf70
bump all versions (due to source-map upgrade)
2014-11-25 09:06:26 -08:00
Geoff Schmidt
34505c8356
Move browser-policy docs from docs.meteor.com to the browser-policy readme. Also create placeholder readmes for the other browser-policy-* packages.
2014-10-13 21:54:04 -07:00
Sashko Stubailo
36da5aecb4
Make all version numbers not have rc
2014-10-13 14:09:37 -07:00
Sashko Stubailo
698fbedb10
Bump all of the version numbers to rc.0
2014-10-07 17:10:48 -07:00
Sashko Stubailo
1e53f6b598
Bump all version numbers again after cherry-picking unipackage fix
2014-10-01 17:06:57 -07:00
Sashko Stubailo
0129c3f5ac
Bump all of the version numbers again, to republish with the unipackage.json fix
2014-10-01 15:43:05 -07:00
Sashko Stubailo
eecc272e4a
Bump every single package version number due to a change in compilation
2014-09-29 23:44:50 -07:00
ekatek
bab557d49b
incrementing package versions for a clean release
2014-09-25 18:34:34 -07:00
ekatek
220cc69e31
package versions incremented
2014-09-19 21:16:14 -07:00
ekatek
fb709c9563
remove versions files from core packages
2014-06-16 22:11:31 -07:00
David Glasser
e4000c6808
Merge branch 'devel' into packaging
...
Conflicts (around utils.quotemeta):
tools/packages.js
tools/utils.js
2014-05-12 17:06:11 -07:00
ekatek
beb0e59b9d
new version files from teh new solver? Also, package.js correct with tests
2014-05-09 17:36:25 -07:00
Emily Stark
c044786e2f
nim, glasser comments
2014-05-08 12:12:45 -07:00
Emily Stark
a8673d01cd
Set X-Content-Type-Options in browser-policy-content
2014-05-08 12:12:45 -07:00
ekatek
031890d2c5
don't store buildtime deps in the catalog
2014-05-04 16:56:58 -07:00
ekatek
23ad149a78
better versions files
2014-04-25 15:06:45 -07:00
ekatek
10d2047d12
clean up
2014-04-25 15:01:20 -07:00
ekatek
c84c8d6097
alphabetize package version lock files
2014-04-24 18:18:21 -07:00
David Glasser
3d3bdd4f50
versions.json update (these should be sorted!)
2014-04-24 17:02:46 -07:00
ekatek
1f3daac20c
remaining versions.json
2014-04-21 19:03:09 -07:00
Geoff Schmidt
66b7253695
Take all packages to 1.0.0 (that aren't already there)
2014-03-07 12:00:20 -08:00
Emily Stark
bdf6fd2485
Use regex to replace trailing slashes from browser-policy URLs.
...
Thanks glasser!
2014-01-13 18:27:58 -08:00
Emily Stark
189845f1fb
Add frame-src to browser-policy-content.
2014-01-11 20:43:36 -08:00
Emily Stark
f89941412a
Smooth over some cross-browser CSP differences.
...
* Adding "foo.com" to your CSP via browser-policy now adds both
"http://foo.com " and "https://foo.com ". This smooths over the fact
that some browsers interpret "foo.com" as "http://foo.com " and some
interpret it as http AND https.
* Trim trailing slashes from origins. Firefox does not allow content
from foo.com if you add "foo.com/" to your CSP.
2014-01-11 20:36:01 -08:00
Emily Stark
de05d27cf3
Make browser-policy-content tell webapp about inline script policy.
...
This avoids the need for webapp to probe for browser-policy without
weak-depending on it.
2013-10-09 12:00:23 -07:00
Emily Stark
a7007ec12b
Actually save csp in cachedCsp.
...
Also rename ensureDirective to prepareForCspDirective to make it clearer that it
clears cachedCsp.
2013-10-03 13:56:03 -07:00
Emily Stark
6f94e8dbd0
Cache csp instead of constructing it each request.
2013-10-03 13:56:03 -07:00
Emily Stark
b5286b941a
Separate browser policy functions into two packages.
...
* browser-policy uses browser-policy-framing and browser-policy-content, both of
which set default policies when they are used. This way you get a default
policy when you add a browser policy package, but you can pick and choose
different packages if you only want to think about one of them.
* The two packages use different namespaces: BrowserPolicy.framing and
BrowserPolicy.content, which meant some functions got renamed (e.g. not using
"framing" or "content in the function name when it's already in the
namespace).
2013-10-03 13:56:03 -07:00
