Squashed commit of the following:

commit 94d217c
Author: Ryan Johnson <ryan.johnson@broadcom.com>
Date:   Mon Feb 23 22:02:37 2026 -0500

    docs: fix typos and grammer (#667)

    Addressed spelling, grammar, and phrasing.

    Signed-off-by: Ryan Johnson <ryan.johnson@broadcom.com>

commit 09e41b6
Author: Ryan Johnson <ryan.johnson@broadcom.com>
Date:   Mon Feb 23 22:02:02 2026 -0500

    chore: remove `.go-version` (#666)

    Removed the`.go-version` now that all workflows that use `actions/setup-go` now get the version from the module in `go.mod`.

    Signed-off-by: Ryan Johnson <ryan.johnson@broadcom.com>

commit 2c7c9c5
Author: Ryan Johnson <ryan@tenthirtyam.org>
Date:   Sun Feb 22 12:09:06 2026 -0500

    docs: update examples url (#664)

    Replaced references to `github.com/vmware-samples/packer-examples-for-vsphere` with `github.com/vmware/packer-examples-for-vsphere`.

    Signed-off-by: Ryan Johnson <ryan@tenthirtyam.org>

commit 2c771b3
Author: Ryan Johnson <ryan@tenthirtyam.org>
Date:   Sun Feb 22 12:01:24 2026 -0500

    docs: update `README.md` (#663)

    Update `README.md`.

    Signed-off-by: Ryan Johnson <ryan@tenthirtyam.org>

commit d17cc76
Author: Ryan Johnson <ryan@tenthirtyam.org>
Date:   Sun Feb 22 11:37:43 2026 -0500

    chore(gh): update release workflow tag pattern (#662)

    Replaced broad `v*` tag filter with a more specific pattern: `v*.*.*` to match stable SemVer releases (e.g. `v2.2.0`) and pre-releases (e.g. `v2.2.0-beta`, `v2.2.0-rc.1`).

    Signed-off-by: Ryan Johnson <ryan@tenthirtyam.org>

commit 6632d05
Author: Ryan Johnson <ryan.johnson@broadcom.com>
Date:   Sat Feb 21 12:14:40 2026 -0500

    chore: update `CODEOWNERS` (#661)

    Update `CODEOWNERS`.

    Signed-off-by: Ryan Johnson <ryan@tenthirtyam.org>

commit 224d5a3
Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Date:   Fri Feb 20 10:16:58 2026 -0500

    chore(deps): bump actions/stale from 10.1.1 to 10.2.0 (#660)

    Bumps [actions/stale](https://github.com/actions/stale) from 10.1.1 to 10.2.0.
    - [Release notes](https://github.com/actions/stale/releases)
    - [Changelog](https://github.com/actions/stale/blob/main/CHANGELOG.md)
    - [Commits](actions/stale@9971854...b5d41d4)

    ---
    updated-dependencies:
    - dependency-name: actions/stale
      dependency-version: 10.2.0
      dependency-type: direct:production
      update-type: version-update:semver-minor
    ...

    Signed-off-by: dependabot[bot] <support@github.com>
    Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

commit dee83a3
Author: Ryan Johnson <ryan.johnson@broadcom.com>
Date:   Fri Feb 20 08:07:54 2026 -0500

    docs: update `CONTRIBUTING.md` (#658)

    Revised the `CONTRIBUTING.md`.

    Signed-off-by: Ryan Johnson <ryan.johnson@broadcom.com>

commit 8587200
Author: Ryan Johnson <ryan.johnson@broadcom.com>
Date:   Wed Feb 18 12:56:13 2026 -0500

    chore(dev): prepare development cycle (#656)

    Prepare the plugin for the 2.2.0 development cycle and pre-release builds.

    Signed-off-by: Ryan Johnson <ryan.johnson@broadcom.com>

Author: tenthirtyam

CODE_OF_CONDUCT.md .github/CODE_OF_CONDUCT.mdCODE_OF_CONDUCT.md renamed to .github/CODE_OF_CONDUCT.md

@@ -1,71 +1,88 @@
 # Contributing Guidelines
 
-Thank you for your interest in contributing to our project. Whether it's a bug
-report, new feature, correction, or additional documentation, we greatly value
-feedback and contributions from our community.
-
-Please read through this document before submitting any issues or pull requests
-to ensure we have all the necessary information to effectively respond to your
-bug report or contribution.
-
-## Reporting Bugs and Suggesting Enhancements
-
-We welcome you to use the [GitHub issues][gh-issues] to report bugs or suggest
-enhancements.
-
-When filing an issue, please check existing open, or recently closed, issues to
-make sure someone else hasn't already reported.
-
-Please try to include as much information as you can using the issue form.
-Details like these are incredibly useful:
-
-- A reproducible test case or series of steps.
-- Any modifications you've made relevant to the bug.
-- Anything unusual about your environment or deployment.
-
-## Contributing via Pull Requests
-
-Contributions using pull requests are appreciated.
-
-**Before** sending us a pull request, please ensure that:
-
-1. You [open a discussion][gh-discussions] to discuss any significant work with
-   the maintainer(s).
-2. You [open an issue][gh-issues] and link your pull request to the issue for
-   context.
-3. You are working against the latest source on the `main` branch.
-4. You check existing open, and recently merged, pull requests to make sure
-   someone else hasn't already addressed the problem.
-
-To open a pull request, please:
-
-1. Fork the repository.
-2. Modify the source; please focus on the **specific** change you are
-   contributing.
-3. Ensure local tests pass.
-4. Update the documentation, if required.
-5. Sign-off and commit to your fork
-   [using clear commit messages][git-commit]. Please use
-   [Conventional Commits][conventional-commits].
-6. Open a pull request, answering any default questions in the pull request.
-7. Pay attention to any automated failures reported in the pull request, and
-   stay involved in the conversation.
-
-GitHub provides additional documentation on [forking a repository][gh-forks] and
-[creating a pull request][gh-pull-requests].
+We greatly value feedback and contributions from our community.
+
+Please review this document before submitting any issues or pull requests to ensure we
+have all the necessary information to effectively collaborate on your contribution.
+
+> [!TIP]
+If you need help or have questions about using the plugin, please refer to the
+[documentation](https://github.com/vmware/packer-plugin-vsphere/tree/main/docs) or open
+a [discussion][gh-discussions].
+
+## Issues
+
+Use [GitHub issues][gh-issues] to report bugs or suggest enhancements using the
+following guidelines.
+
+> [!WARNING]
+> Issues that do not follow the guidelines may be closed by the maintainers without
+> further investigation.
+
+Before opening an issue, please [search existing issues](https://github.com/vmware/packer-plugin-vsphere/issues?q=is%3Aissue+is%3Aopen+label%3Abug)
+to avoid duplicates.
+
+When opening an issue, use the provided issue form to ensure that you provide all the
+necessary details. These details are important for maintainers to understand and
+reproduce the issue.
+
+> [!IMPORTANT]
+> - Ensure that you are using a recent version of the plugin.
+> - Ensure that you are using a supported version of VMware vSphere. The plugin supports versions in accordance with the [Broadcom Product Lifecycle][product-lifecycle].
+
+> [!TIP]
+> - Learn about [formatting code on GitHub](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#quoting-code).
+> - Learn about [referencing issues](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#referencing-issues-and-pull-requests).
+> - Learn about [creating a GitHub Gist](https://docs.github.com/en/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists).
+
+## Pull Requests
+
+Use GitHub pull requests to propose changes to the codebase using the following guidelines.
+
+> [!WARNING]
+> Pull requests that do not follow the guidelines may be closed by the maintainers
+> without further review.
+
+**Before** submitting a pull request, ensure that:
+
+1. You have [opened a discussion][gh-discussions] to discuss any **significant** work with
+   the maintainer(s). This ensures that your contribution is aligned with the
+   project's direction and avoids unnecessary work.
+2. You have identified or [open an issue][gh-issues]. This ensures that your contribution
+   focuses on a specific topic and avoids duplicating effort.
+3. You have forked the repository. Refer to the [GitHub documentation][gh-forks] for help.
+3. You are working against the latest source on the `main` branch. You may need to
+   rebase your branch against the latest `main` branch.
+4. You have created a topic branch based on `main`. Do not work directly on the `main` branch.
+5. You have modified the source based on logical units of work. Focus on the specific change
+   you are contributing. Pull requests that contain multiple unrelated changes will be
+   rejected.
+4. You have followed the existing style and conventions of the project. 
+5. You have added tests for your changes.
+5. You have generated the updated documentation and associated assets by running `make generate`.
+5. You have tested building the plugin by running `make build`.
+7. You have tested your changes with a local build of the plugin by running `make dev`.
+9. You have verified all new and existing tests are passing by running `make test`.
+10. You have used [Conventional Commits][conventional-commits] format for commit messages.
+11. You have signed-off and committed your changes [using clear commit messages][git-commit].
+
+When opening a pull request, ensure that:
+
+1. You title your pull request using the [Conventional Commits][conventional-commits] format.
+2. You provide a detailed description of the changes in the pull request template.
+2. You open any work-in-progress pull requests as a draft.
+3. You mark the pull request as ready for review when you are ready for it to be reviewed.
+4. You follow the status checks for the pull request to ensure that all checks are passing. 
+5. You stay involved in the conversation with the maintainers to ensure that your contribution
+   can be reviewed.
+
+> [!TIP]
+> If you have any questions about the contribution process, open a [discussion][gh-discussions].
 
 ### Contributor Flow
 
 This is an outline of the contributor workflow:
 
-- Create a topic branch from where you want to base your work.
-- Make commits of logical units.
-- Make sure your commit messages are
-  [in the proper format][conventional-commits].
-- Push your changes to the topic branch in your fork.
-- Submit a pull request. If the pull request is a work in progress, please open
-  as draft.
-
 Example:
 
 ```shell
@@ -82,7 +99,7 @@ git push origin feat/add-x
 
 ### Formatting Commit Messages
 
-We follow the conventions on [How to Write a Git Commit Message][git-commit] and
+Follow the conventions on [How to Write a Git Commit Message][git-commit] and use
 [Conventional Commits][conventional-commits].
 
 Be sure to include any related GitHub issue references in the commit message.
@@ -99,7 +116,7 @@ Signed-off-by: Jane Doe <jdoe@example.com>
 Ref: #123
 ```
 
-### Staying In Sync With Upstream
+### Stay In Sync With Upstream
 
 When your branch gets out of sync with the `upstream/main` branch, use the
 following to update:
@@ -130,22 +147,20 @@ If you need to squash changes into an earlier commit, you can use:
 ```shell
 git add .
 git commit --fixup <commit>
-git rebase --interactive --autosquash upsstream/main
+git rebase --interactive --autosquash upstream/main
 git push --force-with-lease origin feat/add-x
 ```
 
-Be sure to add a comment to the pull request indicating your new changes are
-ready to review, as GitHub does not generate a notification when you `git push`.
-
-## Finding Contributions to Work On
+When resolving review comments, mark the conversation as resolved and note the commit
+SHA that addresses the review comment. This helps maintainers verify the issue has been
+resolved.
 
-Looking at the existing issues is a great way to find something to contribute
-on. If you have an idea you'd like to discuss,
-[open a discussion][gh-discussions].
+Request a review from the maintainers when you are ready for a follow-up review.
 
 [conventional-commits]: https://conventionalcommits.org
 [gh-discussions]: https://github.com/vmware/packer-plugin-vsphere/discussions
 [gh-forks]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo
 [gh-issues]: https://github.com/vmware/packer-plugin-vsphere/issues
 [gh-pull-requests]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
 [git-commit]: https://cbea.ms/git-commit
+[product-lifecycle]: https://support.broadcom.com/group/ecx/productlifecycle

.github/CONTRIBUTING.md

@@ -6,7 +6,7 @@ name: Release
 on:
   push:
     tags:
-      - 'v*'
+      - 'v*.*.*' # Match release tags (stable and pre-releases), e.g. v1.2.3, v1.2.3-rc.1
 
 permissions:
   contents: write

.github/workflows/release.yml

@@ -15,7 +15,7 @@ jobs:
       issues: write
       pull-requests: write
     steps:
-      - uses: actions/stale@997185467fa4f803885201cee163a9f38240193d # v10.1.1
+      - uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f # v10.2.0
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
           days-before-stale: 360

.github/workflows/stale.yml

@@ -347,7 +347,7 @@ JSON Example:
 
 <!-- Code generated from the comments of the ConfigParamsConfig struct in builder/vsphere/common/step_config_params.go; DO NOT EDIT MANUALLY -->
 
-- `configuration_parameters` (map[string]string) - A map of key-value pairs to sent to the [`extraConfig`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html#extraConfig).
+- `configuration_parameters` (map[string]string) - A map of key-value pairs to send to the [`extraConfig`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html#extraConfig).
   in the vSphere API's `VirtualMachineConfigSpec`.
 
   HCL Example:
@@ -371,7 +371,7 @@ JSON Example:
   ```
 
   ~> **Note:** Configuration keys that would conflict with parameters that
-  are explicitly configurable through other fields in the `ConfigSpec`` object
+  are explicitly configurable through other fields in the `ConfigSpec` object
   are silently ignored. Refer to the [`VirtualMachineConfigSpec`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html)
   in the vSphere API documentation.
 
@@ -965,10 +965,10 @@ wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/foo/bar/preseed.cfg
 - `floppy_dirs` ([]string) - A list of directories to copy files from.
 
 - `floppy_content` (map[string]string) - Key/Values to add to the floppy disk. The keys represent the paths, and
-  the values contents. It can be used alongside `floppy_files` or
+  the value contents. It can be used alongside `floppy_files` or
   `floppy_dirs`, which is useful to add large files without loading them
-  into memory. If any paths are specified by both, the contents in
-  `floppy_content` will take precedence.
+  into memory. If both specify a path, the contents in `floppy_content` will take
+  precedence.
 
   HCL Example:
 
@@ -980,8 +980,8 @@ wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/foo/bar/preseed.cfg
   ```
 
 - `floppy_label` (string) - The label to use for the floppy disk that is attached when the virtual
-  machine is booted. This is most useful for cloud-init, Kickstart or other
-  early initialization tools, which can benefit from labelled floppy disks.
+  machine is booted. This is most useful for cloud-init, Kickstart, or other
+  early initialization tools, which can benefit from labeled floppy disks.
   By default, the floppy label will be 'packer'.
 
 <!-- End of code generated from the comments of the FloppyConfig struct in builder/vsphere/common/step_add_floppy.go; -->
@@ -993,8 +993,7 @@ wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/foo/bar/preseed.cfg
 
 <!-- Code generated from the comments of the ConnectConfig struct in builder/vsphere/common/step_connect.go; DO NOT EDIT MANUALLY -->
 
-- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance
-  instance.
+- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance.
 
 - `username` (string) - The username to authenticate with the vCenter instance.
 

.go-version

@@ -14,7 +14,7 @@ their respective End of General Support dates. For detailed information, refer t
 - Basic examples are available in the [examples](https://github.com/vmware/packer-plugin-vsphere/tree/main/examples/)
   directory of the GitHub repository.
 
-- Additional examples are available in the [`vmware-samples/packer-examples-for-vsphere`](https://github.com/vmware-samples/packer-examples-for-vsphere)
+- Additional examples are available in the [`vmware/packer-examples-for-vsphere`](https://github.com/vmware/packer-examples-for-vsphere)
   GitHub repository maintained by VMware by Broadcom.
 
 ## Configuration Reference
@@ -107,8 +107,7 @@ wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/foo/bar/preseed.cfg
 
 <!-- Code generated from the comments of the ConnectConfig struct in builder/vsphere/common/step_connect.go; DO NOT EDIT MANUALLY -->
 
-- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance
-  instance.
+- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance.
 
 - `username` (string) - The username to authenticate with the vCenter instance.
 
@@ -182,7 +181,7 @@ wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/foo/bar/preseed.cfg
 
 - `convert_to_template` (bool) - Convert the virtual machine to a template after the build is complete.
   Defaults to `false`.
-  If set to `true`, the virtual machine can not be imported into a content library.
+  If set to `true`, the virtual machine cannot be imported into a content library.
 
 - `export` (\*common.ExportConfig) - The configuration for exporting the virtual machine to an OVF.
   The virtual machine is not exported if [export configuration](#export-configuration) is not specified.
@@ -652,10 +651,10 @@ boot time.
 - `floppy_dirs` ([]string) - A list of directories to copy files from.
 
 - `floppy_content` (map[string]string) - Key/Values to add to the floppy disk. The keys represent the paths, and
-  the values contents. It can be used alongside `floppy_files` or
+  the value contents. It can be used alongside `floppy_files` or
   `floppy_dirs`, which is useful to add large files without loading them
-  into memory. If any paths are specified by both, the contents in
-  `floppy_content` will take precedence.
+  into memory. If both specify a path, the contents in `floppy_content` will take
+  precedence.
 
   HCL Example:
 
@@ -667,8 +666,8 @@ boot time.
   ```
 
 - `floppy_label` (string) - The label to use for the floppy disk that is attached when the virtual
-  machine is booted. This is most useful for cloud-init, Kickstart or other
-  early initialization tools, which can benefit from labelled floppy disks.
+  machine is booted. This is most useful for cloud-init, Kickstart, or other
+  early initialization tools, which can benefit from labeled floppy disks.
   By default, the floppy label will be 'packer'.
 
 <!-- End of code generated from the comments of the FloppyConfig struct in builder/vsphere/common/step_add_floppy.go; -->
@@ -1617,7 +1616,7 @@ JSON Example:
 
 <!-- Code generated from the comments of the ConfigParamsConfig struct in builder/vsphere/common/step_config_params.go; DO NOT EDIT MANUALLY -->
 
-- `configuration_parameters` (map[string]string) - A map of key-value pairs to sent to the [`extraConfig`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html#extraConfig).
+- `configuration_parameters` (map[string]string) - A map of key-value pairs to send to the [`extraConfig`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html#extraConfig).
   in the vSphere API's `VirtualMachineConfigSpec`.
 
   HCL Example:
@@ -1641,7 +1640,7 @@ JSON Example:
   ```
 
   ~> **Note:** Configuration keys that would conflict with parameters that
-  are explicitly configurable through other fields in the `ConfigSpec`` object
+  are explicitly configurable through other fields in the `ConfigSpec` object
   are silently ignored. Refer to the [`VirtualMachineConfigSpec`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html)
   in the vSphere API documentation.
 

.web-docs/components/builder/vsphere-clone/README.md

@@ -76,8 +76,7 @@ virtual machine can be used in the vSphere Clone builder to select a template.
 
 <!-- Code generated from the comments of the ConnectConfig struct in builder/vsphere/common/step_connect.go; DO NOT EDIT MANUALLY -->
 
-- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance
-  instance.
+- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance.
 
 - `username` (string) - The username to authenticate with the vCenter instance.
 

.web-docs/components/builder/vsphere-iso/README.md

@@ -85,7 +85,7 @@ The following configuration options are available for the post-processor.
   same as the source virtual machine's.
 
   This option is useful when deploying to vCenter instance or an ESX host whose
-  version is different than the one used to create the artifact.
+  version is different from the one used to create the artifact.
 
   Refer to [KB 315655](https://knowledge.broadcom.com/external/article?articleNumber=315655)
   for more information on supported virtual hardware versions.

.web-docs/components/data-source/virtualmachine/README.md

@@ -1 +1 @@
-* @tenthirtyam @hashicorp/packer 
+* @vmware/packer-plugin-vsphere-maintainers