chore(master): release 0.13.0

[github-actions]

🤖 I have created a release beep boop

0.13.0 (2023-09-11)

⚠ BREAKING CHANGES

• plugin list exit code 0 when no plugins are installed (#1597)
• 0 exit code for success when adding an existing plugin (#1598)
• fish: don't resolve symlinks for ASDF_DIR (#1583)

Features

• add plugin location when update the plugin (#1602) (36c7024)

Patches

• plugin list exit code 0 when no plugins are installed (#1597) (a029c00)
• 0 exit code for success when adding an existing plugin (#1598) (4dd1904)
• fish: don't resolve symlinks for ASDF_DIR (#1583) (d1a563d)
• improve lint and test scripts (#1607) (b320803)
• Make asdf.fish compatible with Fish 3.1.2 (#1590) (e83d71e)
• no longer write temporary files to home directory (#1592) (624604a)
• nushell language syntax update (#1624) (0ddab5d)
• set default shell version values on POSIX entrypoint (#1594) (4d5f22d)
• warn when any ./lib/commands are marked as executable (#1593) (2043a09)

Documentation

• bin/latest-stable empty query is set to default (#1591) (299dc97)
• migrate to VitePress from VuePress (#1578) (5133819)
• upgrade deps & fix breaking changes (446f8c5)

---

This PR was generated with Release Please. See documentation.

[jthegedus]

migrate to VitePress from VuePress (#1578) (5133819)

This change was the first to occur before any other changes after the last release. It caused Release Please to create a patch-level release. This was not expected. I think it is a bug in Release-Please.

asdf/.github/workflows/release.yml

Line 21 in 5133819

{ "type": "docs", "section": "Documentation", "hidden": false }

Configuration to show docs: commits in the Changelog should not also make these commits get considered for version increments 🤔

Related googleapis/release-please#1745

[hyperupcall]

I was thinking the next release (bugfix release) could be done after the following are merged or resolved:

• fix!: exit success when adding an already-added plugin #1598
• fix!: plugin list exit code 0 when no plugins are installed #1597
• fix: Set default shell version values on POSIX entrypoint #1594
• fix: Show warning when any ./lib/commands are marked as executable #1593
• fix: no longer write temporary files to home directory #1592
• docs: do not hint that the query for bin/latest-stable may be empty #1591
• fix: Make asdf.fish compatible with Fish 3.1.2 #1590
• feat: add plugin location when update the plugin #1602

Thoughts?

I was hoping that the next version could have a version of 0.12.1 (IMO #1583 was a non-breaking-change patch). If it's easy to fix and there is agreement, then I think it would be nice to do. If not, then I don't really mind a full minor-version increment too-too much.

In the next feature release, I was hoping to implement #1579 (which is a breaking change) and #1599, which is why I wanted to get these bug fixes out of the way.

[hyperupcall]

As a sort of side-note, I was wondering if asdf currently has a general stance on maintainership or if current maintainers were open to adding one?

I was thinking it would be quiet useful if I had the ability to add/remove tags from issues, enable running workflows, merge other people's PRs, etc. the usual stuff. I know ya'll maintainers are pretty busy, so I'm hoping the extra help could be useful. I've been contributing stuff for some time now, so I hope this ask isn't out of the blue or something. 😅

[hyperupcall]

@jthegedus @Stratus3D I am sorry for pinging, but when one (or both) of you have the time, I would really appreciate a comment. Looking to get out a bugfix (and #1579) out sooner rather than later.

[jthegedus]

@hyperupcall Sorry mate, have been afk from OSS the past few weeks. Back at it though! I will review most of these over the coming days.

[hyperupcall]

@jthegedus I understand, it can be difficult finding time for open source - you'll get to them when you get to them. If you feel comfortable adding me as a maintainer, I would be happy to help review others' PRs like I mentioned before. Also I know I'm a week late in responding and you are still busy, so I just wanted be explicit and say I'm not trying to be passive-aggressive with the timing of my response and everything I said was genuine.

[jthegedus]

@jthegedus I understand, it can be difficult finding time for open source - you'll get to them when you get to them. If you feel comfortable adding me as a maintainer, I would be happy to help review others' PRs like I mentioned before. Also I know I'm a week late in responding and you are still busy, so I just wanted be explicit and say I'm not trying to be passive-aggressive with the timing of my response and everything I said was genuine.

Adding you as a maintainer is something I've been thinking about for some time and will definitely discuss with @Stratus3D about very soon.

Again, sorry for the delays here. Your help has been greatly appreciated as has your patience 😃

[jthegedus]

Going to finally cut this release 😅

[github-actions]

🤖 Release is at https://github.com/asdf-vm/asdf/releases/tag/v0.13.0 🌻