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

Age	Commit message (Collapse)	Author
2024-09-12	test: remove `DENO_FUTURE` (#25587)	Asher Gomez

2024-09-04	chore(tty): soft-remove `Deno.isatty()` (#25410)	Asher Gomez
	Towards #22079
2024-08-26	Reland "test: run unit tests with DENO_FUTURE=1" (#25212)	Bartek Iwańczuk
	Reverted in https://github.com/denoland/deno/pull/25060
2024-08-15	Revert "test: run unit tests with DENO_FUTURE=1 (#24400)" (#25060)	Bartek Iwańczuk
	This reverts commit 22a834ff5b4b312b8f91be8991f2b495d49fad2f. Appears this commit might have broken tests on `main`.
2024-08-14	test: run unit tests with DENO_FUTURE=1 (#24400)	Bartek Iwańczuk
	This commit adds another test suite that runs all Deno unit tests with `DENO_FUTURE=1` flag to ensure all APIs are working as expected, once Deno 2 is released. --------- Co-authored-by: Divy Srivastava <dj.srivastava23@gmail.com>
2024-06-05	chore: upgrade dlint to 0.60.0 (#24041)	Bartek Iwańczuk
	Factoring out `dlint` upgrade from https://github.com/denoland/deno/pull/24034 as it requires us to change the lint step on mac to use ARM runners. --------- Co-authored-by: Luca Casonato <hello@lcas.dev> Co-authored-by: David Sherret <dsherret@users.noreply.github.com>
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.