deno.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2024-09-18	tests: re-enable upgrade tests (#25680)	Luca Casonato

2024-08-31	fix(upgrade): more informative information on invalid version (#25319)	Bartek Iwańczuk
	Before: ``` $ deno upgrade v1.xx error: Invalid version passed ``` After: ``` $ deno upgrade v1.xx error: Invalid version passed (v1.xx) Example usage: deno upgrade \| deno upgrade 1.46 \| deno upgrade canary ``` Also updates help text to use "shorthand version" without flags, but a positional arg.
2024-08-12	chore: mark upgrade_prompt as flaky (#25009)	David Sherret

2024-08-02	feat(unstable/fmt): move yaml formatting behind unstable flag (#24848)	David Sherret
	This moves YAML formatting behind an unstable flag for Deno 1.46. This will make it opt-in to start and then we can remove the flag to make it on by default in version of Deno after that. This can be specified by doing `deno fmt --unstable-yaml` or by specifying the following in a deno.json file: ```json { "unstable": ["fmt-yaml"] } ```
2024-08-02	chore: mark upgrade_invalid_canary_version as flaky (#24833)	David Sherret

2024-07-29	chore: mark upgrade invalid lockfile as flaky (#24760)	David Sherret
	Closes #24759
2024-07-23	fix(upgrade): do not error if config in cwd invalid (#24689)	David Sherret
	``` > deno upgrade error: Unsupported lockfile version 'invalid'. Try upgrading Deno or recreating the lockfile. V:\scratch > V:\deno\target\debug\deno upgrade Looking up latest version Local deno version 1.45.3 is the most recent release ``` Closes #24517 Closes #20729
2024-02-10	chore: move cli/tests/ -> tests/ (#22369)	Matt Mastracci
	This looks like a massive PR, but it's only a move from cli/tests -> tests, and updates of relative paths for files. This is the first step towards aggregate all of the integration test files under tests/, which will lead to a set of integration tests that can run without the CLI binary being built. While we could leave these tests under `cli`, it would require us to keep a more complex directory structure for the various test runners. In addition, we have a lot of complexity to ignore various test files in the `cli` project itself (cargo publish exclusion rules, autotests = false, etc). And finally, the `tests/` folder will eventually house the `test_ffi`, `test_napi` and other testing code, reducing the size of the root repo directory. For easier review, the extremely large and noisy "move" is in the first commit (with no changes -- just a move), while the remainder of the changes to actual files is in the second commit.