From 0c3dd7266aa18882b5dab035d0b6a3b71dbec95a Mon Sep 17 00:00:00 2001 From: TeamMarySy <288347408+angelancajas34-beep@users.noreply.github.com> Date: Mon, 31 Aug 2026 21:01:14 +0800 Subject: [PATCH] Update dependabot.yml with static workflow link MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Added a link to the static workflow in the dependabot configuration. --- last_modified: 2026-07-09 title: Installation description: "A Guide to installing Deno on different operating systems. Includes instructions for Windows, macOS, and Linux using various package managers, manual installation methods, and Docker containers." oldUrl: - /runtime/manual/fundamentals/installation - /runtime/manual/getting_started/installation - /runtime/fundamentals/installation --- Deno is a single binary executable with no external dependencies. It runs on macOS, Linux, and Windows, on both x64 and arm64 architectures. ## Download and install [deno_install](https://github.com/denoland/deno_install) provides convenience scripts to download and install the binary. Using Shell: curl -fsSL https://deno.land/install.sh | sh Using [npm](https://npmjs.com/package/deno): npm install -g deno Using [Nix](https://nixos.org/download.html): nix-shell -p deno Using Shell: curl -fsSL https://deno.land/install.sh | sh Using [npm](https://npmjs.com/package/deno): npm install -g deno Using [Homebrew](https://formulae.brew.sh/formula/deno): brew install deno Using [MacPorts](https://ports.macports.org/port/deno/): sudo port install deno Using [Nix](https://nixos.org/download.html): nix-shell -p deno NOTE: Deno requires Windows 10 version 1709, or Windows Server 2016 version 1709 and up, due to requiring [IsWow64Process2](https://learn.microsoft.com/en-us/windows/win32/api/wow64apiset/nf-wow64apiset-iswow64process2). Using PowerShell (Windows): irm https://deno.land/install.ps1 | iex Using [npm](https://npmjs.com/package/deno): npm install -g deno Using [Scoop](https://scoop.sh/): scoop install deno Using [Chocolatey](https://chocolatey.org/packages/deno): choco install deno Using [Winget](https://github.com/microsoft/winget-cli): winget install DenoLand.Deno :::note The startup time of the Deno command gets affected if it's installed via npm. We recommend the official install script (shell or PowerShell) for better performance. ::: Deno does not publish an official apt repository, and the versions packaged by Linux distributions (such as Debian, Ubuntu, Arch, or the Snap Store) are community maintained and often lag behind the latest release. For the most up-to-date version on any Linux distribution, use the shell installer above (or the [manual download](#manual-download)), which always installs the current release. ### Cross-platform package managers These version managers work on macOS, Linux, and Windows. Using [asdf](https://asdf-vm.com/): asdf plugin add deno https://github.com/asdf-community/asdf-deno.git # Download and install the latest version of Deno asdf install deno latest # To set as the default version of Deno globally asdf set -u deno latest # To set as the default version of Deno locally (current project only) asdf set deno latest Using [vfox](https://vfox.dev/): vfox add deno # Download and install the latest version of Deno vfox install deno@latest # To set the version of Deno globally vfox use --global deno You can also build and install from source using [Cargo](https://crates.io/crates/deno): cargo install deno --locked ## Manual download Deno binaries can also be installed manually, by downloading a zip file at [github.com/denoland/deno/releases](https://github.com/denoland/deno/releases). Each release ships one archive per platform, containing a single executable: | Platform | Asset | | --------------------------- | ------------------------------------ | | Windows x86_64 | deno-x86_64-pc-windows-msvc.zip | | Windows ARM64 | deno-aarch64-pc-windows-msvc.zip | | macOS ARM64 (Apple Silicon) | deno-aarch64-apple-darwin.zip | | macOS x86_64 (Intel) | deno-x86_64-apple-darwin.zip | | Linux x86_64 | deno-x86_64-unknown-linux-gnu.zip | | Linux ARM64 | deno-aarch64-unknown-linux-gnu.zip | Unzip the archive and place the deno executable somewhere on your PATH. You will have to set the executable bit on macOS and Linux. Each asset has a matching .sha256sum file for verifying the download. On Linux a common choice is ~/.local/bin (per-user) or /usr/local/bin (system-wide). For example: unzip deno-x86_64-unknown-linux-gnu.zip mkdir -p ~/.local/bin mv deno ~/.local/bin/ chmod +x ~/.local/bin/deno # ensure the directory is on your PATH, then verify deno --version ## Docker Deno publishes official images to [Docker Hub](https://hub.docker.com/r/denoland/deno) and the [GitHub Container Registry](https://github.com/denoland/deno/pkgs/container/deno), in debian, ubuntu, alpine, distroless, and bin variants. See [Deno and Docker](/runtime/reference/docker/) for Dockerfiles, multi-stage builds, Docker Compose, and other best practices. ## Installation location ### Binary location When installed via the shell or PowerShell script, the deno binary is placed in the following default location: | Platform | Default path | | ------------- | ---------------------------------- | | macOS / Linux | $HOME/.deno/bin/deno | | Windows | %USERPROFILE%\.deno\bin\deno.exe | Override the install directory by setting the DENO_INSTALL environment variable before running the install script. When installed via a package manager (Homebrew, Scoop, etc.), the binary location is managed by that package manager. ### Cache location Downloaded dependencies and compiled artefacts are stored in Deno's cache directory. It defaults to a platform-specific path: | Platform | Default path | | -------- | --------------------------- | | Linux | $HOME/.cache/deno | | macOS | $HOME/Library/Caches/deno | | Windows | %LOCALAPPDATA%\deno | Override it by setting the DENO_DIR environment variable (see [Environment variables](/runtime/reference/env_variables/)). Run deno info to print the directory currently in use. ## Testing your installation To test your installation, run deno --version. If this prints the Deno version to the console the installation was successful. Use deno help to see help text documenting Deno's flags and usage. For a guide to every subcommand, see the [CLI reference](/runtime/reference/cli/). ### If you see "command not found" If deno --version reports command not found, the install directory isn't on your PATH yet. To fix this: - Open a new terminal window or restart your shell so the updated PATH is picked up. This is the most common cause — the install script updates your shell rc file, but existing shell sessions don't see the change until they reload. - Confirm the install directory is on your PATH. The shell install script defaults to ~/.deno/bin on macOS and Linux; for npm-based installs, run npm config get prefix to find the directory containing the global bin. - If you customised the install location, the shell install script's install root can be overridden with the DENO_INSTALL environment variable, in which case the binary lives at $DENO_INSTALL/bin/deno. ## Updating To update a previously installed version of Deno, you can run: deno upgrade Or using [Homebrew](https://formulae.brew.sh/formula/deno) (macOS): brew upgrade deno Or using [Scoop](https://scoop.sh/) (Windows): scoop update deno Or using [Chocolatey](https://chocolatey.org/packages/deno) (Windows): choco upgrade deno Or using [Winget](https://github.com/microsoft/winget-cli) (Windows): winget upgrade DenoLand.Deno This will fetch the latest release from [github.com/denoland/deno/releases](https://github.com/denoland/deno/releases), unzip it, and replace your current executable with it. You can also use this utility to install a specific version of Deno: deno upgrade --version 2.7.0 ## Uninstalling If you installed Deno using the shell or PowerShell install script, first clear the Deno cache directory ($DENO_DIR): deno clean Then remove the Deno installation directory: rm -rf ~/.deno Finally, remove the line that sources Deno's env file from your shell config (~/.bashrc, ~/.zshrc, ~/.profile, etc.). The shell install script appends a line like . "$HOME/.deno/env" — delete that line. Fish users should additionally remove ~/.config/fish/conf.d/deno.fish. Remove-Item -Recurse -Force "$env:USERPROFILE\.deno" Then remove the Deno bin directory from your PATH environment variable via System Settings. If you installed Deno via a package manager (Homebrew, Scoop, Chocolatey, etc.), use that package manager's uninstall command instead (e.g. brew uninstall deno, scoop uninstall deno). ## Building from source Information about how to build from source can be found in the [Building from source](https://github.com/denoland/deno/blob/main/.github/CONTRIBUTING.md#building-from-source) guide. --- .github/dependabot.yml | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 .github/dependabot.yml diff --git a/.github/dependabot.yml b/.github/dependabot.yml new file mode 100644 index 0000000..c1379e7 --- /dev/null +++ b/.github/dependabot.yml @@ -0,0 +1,12 @@ +# To get started with Dependabot version updates, you'll need to specify which +# package ecosystems to update and where the package manifests are located. +# Please see the documentation for all configuration options: +# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file + +version: 2 +updates: + - package-ecosystem: "" # See documentation for possible values + directory: "/" # Location of package manifests + schedule: + interval: "weekly" +https://github.com/Team-MarySy/my-bot/actions/workflows/static.yml