Merge 15337dfd71 into c8445c45a9

See [here](https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/) for more explanations:
> We are monitoring telemetry for the usage of these commands and plan to fully disable them on 31st May 2023. Starting 1st June 2023 workflows using save-state or set-output commands via stdout will fail with an error.

README.md

@@ -10,7 +10,7 @@ pairing with smart people at Hashrocket.
 
 For a steady stream of TILs, [sign up for my newsletter](https://crafty-builder-6996.ck.page/e169c61186).
 
-_1608 TILs and counting..._
+_1609 TILs and counting..._
 
 See some of the other learning resources I work on:
 - [Ruby Operator Lookup](https://www.visualmode.dev/ruby-operators)
@@ -691,6 +691,7 @@ If you've learned something here, support my efforts writing daily TILs by
 ### Mise
 
 - [List The Files Being Loaded By Mise](mise/list-the-files-being-loaded-by-mise.md)
+- [Read Existing Dot Env File Into Env Vars](mise/read-existing-dot-env-file-into-env-vars.md)
 
 ### MongoDB
 

github-actions/capture-an-output-value-for-use-in-a-later-step.md

@@ -23,11 +23,11 @@ version from my `.tool-versions` file with a step that uses `set-output`.
   - name: Read Node.js version to install from `.tool-versions`
     id: nodejs
     run: >-
-      echo "::set-output name=NODE_VERSION::$(
+      echo "NODE_VERSION=$(
         cat .tool-versions |
         grep nodejs |
         sed 's/nodejs \(.*\)$/\1/'
-      )"
+      )" >> $GITHUB_OUTPUT
 ```
 
 `echo` runs the command in the string which sets `NODE_VERSION` as an output
@@ -45,4 +45,4 @@ This output value can be referenced in a later step.
 `steps` has a reference to the `nodejs` step (note the `id` above) which then
 has `outputs` like the `NODE_VERSION`.
 
-[source](https://docs.github.com/en/actions/reference/workflow-commands-for-github-actions#using-workflow-commands-to-access-toolkit-functions)
+[source](https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter)

mise/read-existing-dot-env-file-into-env-vars.md

@@ -0,0 +1,28 @@
+# Read Existing Dot Env File Into Env Vars
+
+Just about any web app that I've worked on has had a `.env` file as a way of
+configuring aspects of the app specific to that environment. These typically
+are read into the environment with a language-specific
+[dotenv](https://github.com/bkeepers/dotenv) tool.
+
+Mise supports this convention. In addition to specifying individual non-secret
+env vars, you can also instruct `mise` to read-in a `.env` file like so:
+
+```toml
+[env]
+PORT=3344
+_.file = ".env"
+```
+
+The `_.file` line tells `mise` that there is a file `.env` with key-value pairs
+that it should read in. It can even handle `.env.json` and `.env.toml` file
+formats.
+
+To ensure that `mise` is picking up the values from the `.env` file, you can
+run the following command and make sure they show up in the output:
+
+```bash
+$ mise env
+```
+
+[source](https://mise.jdx.dev/environments/secrets.html)