az2aws 1.1.0 → 1.1.1

package/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "1.1.0"
+  ".": "1.1.1"
 }

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## [1.1.1](https://github.com/kuma0128/az2aws/compare/v1.1.0...v1.1.1) (2026-01-19)
+
+
+### Bug Fixes
+
+* update Snapcraft config to use npm plugin ([#59](https://github.com/kuma0128/az2aws/issues/59)) ([e574441](https://github.com/kuma0128/az2aws/commit/e57444187fc37460c3838d973c28563fe9e13913))
+
 ## [1.1.0](https://github.com/kuma0128/az2aws/compare/v1.0.2...v1.1.0) (2026-01-09)
 
 

package/CONTRIBUTING.md

@@ -10,6 +10,7 @@ Thank you for your interest in contributing to az2aws! This document provides gu
 - [Pull Request Process](#pull-request-process)
 - [Coding Standards](#coding-standards)
 - [Commit Message Guidelines](#commit-message-guidelines)
+- [Release Process](#release-process)
 - [Reporting Issues](#reporting-issues)
 
 ## Code of Conduct
@@ -193,7 +194,97 @@ src/
 
 ## Commit Message Guidelines
 
-Commit messages should be generated using some LLM model.
+This project uses [Conventional Commits](https://www.conventionalcommits.org/) for commit messages. The commit message format is used by [release-please](https://github.com/googleapis/release-please) to automatically generate changelogs and determine version bumps.
+
+### Commit Message Format
+
+```
+<type>(<scope>): <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+### Commit Types and Their Effects
+
+| Type | CHANGELOG Section | Release Trigger | Version Bump |
+|------|-------------------|-----------------|--------------|
+| `feat` | Features | Yes | MINOR (1.x.0) |
+| `fix` | Bug Fixes | Yes | PATCH (1.0.x) |
+| `docs` | Not included | No | - |
+| `chore` | Not included | No | - |
+| `refactor` | Not included | No | - |
+| `test` | Not included | No | - |
+| `style` | Not included | No | - |
+| `perf` | Performance Improvements | Yes | PATCH (1.0.x) |
+
+### Breaking Changes
+
+For breaking changes, add `!` after the type or include `BREAKING CHANGE:` in the footer:
+
+```
+feat!: remove deprecated --legacy flag
+
+BREAKING CHANGE: The --legacy flag has been removed. Use --mode instead.
+```
+
+Breaking changes trigger a MAJOR version bump (x.0.0).
+
+### Examples
+
+```sh
+# New feature (triggers MINOR release, appears in CHANGELOG)
+feat: add support for credential_process
+
+# Bug fix (triggers PATCH release, appears in CHANGELOG)
+fix: resolve proxy configuration conflict
+
+# Documentation only (no release, not in CHANGELOG)
+docs: update installation instructions
+
+# If you want documentation changes to appear in CHANGELOG, use feat:
+feat(docs): add mise installation guide
+
+# Maintenance (no release, not in CHANGELOG)
+chore: update dependencies
+```
+
+### Important Notes
+
+- **PR titles matter**: When a PR is squash-merged, the PR title becomes the commit message. Ensure your PR title follows this format.
+- **Use `feat(docs):`** if you want documentation changes to appear in the changelog and trigger a release.
+- Commit messages can be generated using an LLM model, but ensure they follow the Conventional Commits format.
+
+## Release Process
+
+This project uses [release-please](https://github.com/googleapis/release-please) for automated releases.
+
+### How It Works
+
+1. When PRs are merged to `main`, release-please analyzes commit messages
+2. If releasable commits exist (`feat`, `fix`, `perf`, or breaking changes), release-please creates/updates a Release PR
+3. The Release PR contains:
+   - Version bump in `package.json`
+   - Updated `CHANGELOG.md` with all changes since the last release
+4. When the Release PR is merged, a new GitHub release is created with the appropriate tag
+
+### What Triggers a Release
+
+| Commit Type | Triggers Release? | Example |
+|-------------|-------------------|---------|
+| `feat:` | Yes (MINOR) | `feat: add SSO support` |
+| `fix:` | Yes (PATCH) | `fix: handle timeout error` |
+| `perf:` | Yes (PATCH) | `perf: optimize credential caching` |
+| `feat!:` / `BREAKING CHANGE` | Yes (MAJOR) | `feat!: change config format` |
+| `docs:` | No | `docs: update README` |
+| `chore:` | No | `chore: update deps` |
+
+### Tips for Contributors
+
+- If your change should appear in the release notes, use `feat:` or `fix:`
+- For documentation improvements that benefit users, consider using `feat(docs):` to include them in the release
+- Multiple commits of the same type are grouped together in the CHANGELOG
 
 ## Reporting Issues
 

package/README.md

@@ -9,50 +9,60 @@ If your organization uses [Azure Active Directory](https://azure.microsoft.com)
 
 ## Installation
 
-Installation can be done in any of the following platform - Windows, Linux, Docker, Snap
+### mise (Recommended)
 
-### Windows
+[mise](https://mise.jdx.dev/) is a polyglot version manager that can install az2aws directly.
 
-Install [Node.js](https://nodejs.org/) v24 or higher. Then install az2aws with npm:
+Install mise:
 
-    npm install -g az2aws
+    curl https://mise.run | sh
 
-You may need to install puppeteer dependency, if you're getting missing chrome or chromium message
+Activate mise in your shell:
 
-    node <node_modules_dir>/az2aws/node_modules/puppeteer/install.js
+    # For zsh (macOS default)
+    echo 'eval "$(~/.local/bin/mise activate zsh)"' >> ~/.zshrc
+    source ~/.zshrc
 
-### Linux
+    # For bash (Linux default)
+    echo 'eval "$(~/.local/bin/mise activate bash)"' >> ~/.bashrc
+    source ~/.bashrc
 
-In Linux you can either install for all users or just the current user. In either case, you must first install [Node.js](https://nodejs.org/) v24 or higher and any [puppeteer dependencies](https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md#chrome-headless-doesnt-launch). Then follow the appropriate instructions.
+Install az2aws:
 
-#### Option A: Install for All Users
+    mise use -g npm:az2aws
 
-Install az2aws globally with npm:
+### npm
 
-    sudo npm install -g az2aws --unsafe-perm
+Install [Node.js](https://nodejs.org/) v24 or higher, then install az2aws:
 
-Puppeteer doesn't install globally with execution permissions for all users so you'll need to modify them:
+    npm install -g az2aws
 
-    sudo chmod -R go+rx $(npm root -g)
+#### Linux Notes
+
+You must install [puppeteer dependencies](https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md#chrome-headless-doesnt-launch) first.
+
+**Install for all users:**
 
-#### Option B: Install Only for Current User
+    sudo npm install -g az2aws --unsafe-perm
+    sudo chmod -R go+rx $(npm root -g)
 
-First configure npm to install global packages in [your home directory](https://docs.npmjs.com/getting-started/fixing-npm-permissions):
+**Install for current user only:**
 
     mkdir ~/.npm-global
     npm config set prefix '~/.npm-global'
-    export PATH=~/.npm-global/bin:$PATH
-    source ~/.profile
     echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.profile
     source ~/.profile
+    npm install -g az2aws
 
-Then install az2aws:
+#### Windows Notes
 
-    npm install -g az2aws
+If you get a missing Chrome/Chromium error, install the puppeteer dependency manually:
+
+    node <node_modules_dir>/az2aws/node_modules/puppeteer/install.js
 
 ### Docker
 
-A Docker image has been built with az2aws preinstalled. You simply need to run the command with a volume mounted to your AWS configuration directory.
+Run az2aws with a volume mounted to your AWS configuration directory:
 
     docker run --rm -it -v ~/.aws:/root/.aws az2aws/az2aws
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "az2aws",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "Use Azure AD SSO to log into the AWS CLI. A modern, actively maintained alternative to aws-azure-login.",
   "main": "index.js",
   "author": {
@@ -55,6 +55,7 @@
   "dependencies": {
     "@aws-sdk/client-sts": "^3.723.0",
     "@smithy/node-http-handler": "^2.5.0",
+    "az2aws": "^1.1.0",
     "bluebird": "^3.7.2",
     "cheerio": "^1.0.0-rc.10",
     "commander": "^9.5.0",