Avital Oliver
926cf1ca9d
1.1-rc.4
2015-03-28 12:19:05 -07:00
Avital Oliver
d2427c9b8e
1.1-rc.3
2015-03-28 12:17:28 -07:00
Avital Oliver
fa22f400ae
Merge tag 'release/METEOR@1.1-rc.1' into release-1.1
2015-03-28 11:57:04 -07:00
sashko
b6fb6f5444
Change output name
2015-03-27 11:37:31 -07:00
Sashko Stubailo
acee5d0fcc
Bump package versions
2015-03-27 10:37:27 -07:00
Sashko Stubailo
aa597d405a
Bump release version
2015-03-27 10:35:08 -07:00
David Greenspan
3940b29d29
Fix "html scanner" tests when run in isolation
...
...and sometimes when running all tests, seemingly
2015-03-27 09:51:49 -07:00
Avital Oliver
358d797373
Improve error on publish-for-arch with colons
...
It's unfortunate that this change is in `compiler.compile`. It's
actually unfortunate that we only catch this during publish-for-arch.
But it seems too much to disallow all packages published with colons
even if they don't have binary dependencies since a lot of old
packages were created with our command-line tool that created
filenames with colons in them.
2015-03-26 18:46:12 -07:00
David Glasser
d79ca97398
Be clearer that you need to publish for this arch
...
Fixes #3961 .
2015-03-26 17:32:37 -07:00
Avital Oliver
120febbf8a
Fix meteor reset on Windows
...
We were incorrectly always assuming that Meteor is running
by not actually trying to connect to the port that the
MONGO-PORT file reports Mongo is listening to.
The problem is that that file isn't cleared when Meteor
quits or crashes.
Fixes https://github.com/meteor/windows-preview/issues/138
2015-03-26 17:11:17 -07:00
Slava Kim
2b2b721ff4
Reformat the warnings
2015-03-26 17:07:00 -07:00
Slava Kim
0a7cf60294
Add a warning about proxy env variables when a connection in tool fails
2015-03-26 16:58:41 -07:00
David Greenspan
ae09e3fae6
History.md entry for Blaze bug fix
2015-03-26 10:04:22 -07:00
David Greenspan
74adefb781
Avoid recursion when materializing DOM ( Fix #3028 )
...
This way we don't get a stack overflow when materializing nested
Views. Certain browser/OS combinations seem to have particularly
low budgets (especially Firefox/Windows apparently).
Verified by running https://github.com/mxab/meteor-call-stack-exceed
on Chrome/Mac. Nesting limit used to be about 160, but now you get
unlimited nesting (tried up to 10,000, which renders in about 7-8
seconds).
Tested for correctness by running all package tests.
2015-03-26 09:54:41 -07:00
David Greenspan
8c1334d9fc
Replace DOMMaterializer visitor with a function
...
This already reduces stack usage, allowing deeper recursion,
but we'll see if we can reduce it even more.
2015-03-26 09:54:32 -07:00
Slava Kim
c9fd50d0f4
Merge branch 'tracker-errors' into release-1.1
2015-03-25 19:33:56 -07:00
Slava Kim
858813c2ef
Add history.md remarks for #3822
2015-03-25 19:33:02 -07:00
sashko
f80fa24b64
Fix build script, and un-cache tarball
2015-03-25 19:20:26 -07:00
Sashko Stubailo
3a1c896ed3
Merge pull request #4029 from meteor/wap
...
Wipe All Packages on Windows
2015-03-25 18:36:04 -07:00
Slava Kim
ac15655897
Remove stray if statemet
...
A leftover from debugging
2015-03-25 18:25:04 -07:00
Slava Kim
9305e9d514
Adapt wipe-all-packages command to Windows layout
2015-03-25 17:16:46 -07:00
Slava Kim
a1fefa9f92
Fix wipe-all-packages test for Windows
2015-03-25 17:16:46 -07:00
Slava Kim
7e03f78b80
Be able to parse absolute and relative paths in meteor.bat
2015-03-25 17:16:46 -07:00
Slava Kim
9b12a33c6b
Fix the default release track issue on Windows
2015-03-25 17:16:46 -07:00
Slava Kim
bba6b617a3
Add fake builds in the test
2015-03-25 17:16:46 -07:00
Slava Kim
5337b3b6c6
Fix the test to generate a relative symlink
2015-03-25 17:16:46 -07:00
Slava Kim
d9cc95531b
additional checks in tests to ensure that exactly two versions of tool are not removed
2015-03-25 17:16:46 -07:00
Slava Kim
7be6fe4018
Wipe all packages test
...
Tested on Mac
2015-03-25 17:16:46 -07:00
Sashko Stubailo
0e3e529751
Add command to test wipeAllPackages
2015-03-25 17:16:46 -07:00
Sashko Stubailo
21723a0668
Update heading
2015-03-25 17:00:47 -07:00
Sashko Stubailo
8a27c44464
Add Windows to History.md
2015-03-25 17:00:02 -07:00
Sashko Stubailo
46d6de3106
Re-run docs script
2015-03-25 16:52:49 -07:00
Sashko Stubailo
fc92ea6858
Bump more versions
2015-03-25 16:21:39 -07:00
Sashko Stubailo
462828572f
Bump release
2015-03-25 16:18:39 -07:00
Sashko Stubailo
26c040179b
Bump a bunch of versions to be the newest
2015-03-25 16:17:48 -07:00
Sashko Stubailo
4ff636c7df
Merge branch 'master' into release-1.1
...
Conflicts:
History.md
2015-03-25 16:07:42 -07:00
Sashko Stubailo
0b2d6b40c0
Update release date in History.md
2015-03-25 14:57:29 -07:00
Sashko Stubailo
993b775043
Merge branch 'release-1.0.5'
2015-03-25 14:56:07 -07:00
Sashko Stubailo
71ea938141
Update all of the examples
2015-03-25 14:55:37 -07:00
Sashko Stubailo
06f35fb5b7
Update docs to 1.0.5 release
2015-03-25 14:53:33 -07:00
Sashko Stubailo
f3e19c37cf
Update release number in the docs
2015-03-25 14:52:46 -07:00
Sashko Stubailo
971247ef47
Update banners for 1.0.5
2015-03-25 14:50:52 -07:00
David Greenspan
e97e29e8b0
Add --allow-incompatible-update to more commands
...
In particular: `create`, `test-packages`, `rebuild`, `publish`,
`publish-for-arch`, `admin run-upgrader`
Add it to the help text for `publish`, and simply force the flag to
true in `create`. Other commands get it as an undocumented flag
in case the version solver tells you to pass it in.
2015-03-25 14:30:59 -07:00
Sashko Stubailo
c3bded9928
Un-rc version numbers for 1.0.5
2015-03-25 13:56:03 -07:00
Sashko Stubailo
1c62efe0cf
Update release number for 1.0.5
2015-03-25 13:54:37 -07:00
sashko
3a748a5ab6
Remove unlinking ssh code that fails
...
We delete temp directories anyway!
2015-03-24 21:37:30 -07:00
sashko
808a276eab
Bundle the boostrap tarball inside the installer
...
At build time
2015-03-24 21:28:50 -07:00
Avital Oliver
a2ec383f0e
Merge remote-tracking branch 'origin/avital-dev-bundle-fstream' into release-1.1
2015-03-24 21:09:54 -07:00
Avital Oliver
178f337882
Remove echo mistakenly left in code
2015-03-24 20:35:11 -07:00
Avital Oliver
c03972b7ca
Allow using test dev bundles on Windows
...
This duplicates logic we had for Mac/Linux that lets you
set a USE_TEST_DEV_BUNDLE_SERVER environment variable
to try running a newly built dev bundle before publishing
it.
2015-03-24 20:28:03 -07:00
