chore: version packages (#12)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: github-actions[bot]

.changeset/auto-detect-repo-from-git-remote.md

@@ -1,5 +1,22 @@
 # @codacy/codacy-cloud-cli
 
+## 1.2.0
+
+### Minor Changes
+
+- [#11](https://github.com/codacy/codacy-cloud-cli/pull/11) [`12ad8a3`](https://github.com/codacy/codacy-cloud-cli/commit/12ad8a30641a903e3d7a914dfd255bc2401287e5) Thanks [@alerizzo](https://github.com/alerizzo)! - Auto-detect provider, organization, and repository from the git remote origin URL. All repository-scoped commands now work without explicitly passing `<provider> <organization> <repository>` — just run them inside a git repo with an `origin` remote pointing at GitHub, GitLab, or Bitbucket.
+
+- [#13](https://github.com/codacy/codacy-cloud-cli/pull/13) [`f039b39`](https://github.com/codacy/codacy-cloud-cli/commit/f039b39922440cb29d2d7e0ea7c7ea5091c3eb42) Thanks [@alerizzo](https://github.com/alerizzo)! - Improve `issues --overview`. The False Positives table now uses human-friendly labels ("Not a False Positive" / "Potential False Positive") instead of the raw `belowThreshold` / `equalOrAboveThreshold` API bucket names. The overview also adds a "Suggested actions to reduce noise" section that flags noisy patterns — those accounting for at least 10% of all issues, or at least 3× the average issues-per-pattern — and prints a ready-to-run `codacy pattern <tool> <patternId> --disable` command for each (the owning tool is resolved automatically; suggestions whose tool can't be resolved are omitted). `--output json` output is unchanged.
+
+- [#13](https://github.com/codacy/codacy-cloud-cli/pull/13) [`f039b39`](https://github.com/codacy/codacy-cloud-cli/commit/f039b39922440cb29d2d7e0ea7c7ea5091c3eb42) Thanks [@alerizzo](https://github.com/alerizzo)! - Make the pattern commands aware of local configuration files and coding standards.
+
+  - `pattern <tool> <patternId>` with no action flag now **shows the pattern's information** (same card as the `patterns` command, with `--output json` support). Since there's no single-pattern endpoint, it searches by ID and keeps the exact match.
+  - When a tool is driven by a local configuration file, `patterns` (list) and `pattern` (info) print `<tool> is using a local configuration file.` and skip fetching patterns; `patterns --enable-all/--disable-all` and `pattern --enable/--disable/--parameter` refuse with `Tool uses a local configuration file, can't be updated.`
+  - `pattern --enable/--disable/--parameter` also refuses patterns enforced by a coding standard with `Pattern enforced by <standard> coding standard, can't be modified.`
+  - `issues --overview` noise suggestions now adapt per pattern: a runnable `codacy pattern … --disable` command when possible, otherwise a manual step — `Update your local <tool> configuration file to disable the pattern` or `Update <coding standard> to disable the pattern`.
+
+- [#13](https://github.com/codacy/codacy-cloud-cli/pull/13) [`f039b39`](https://github.com/codacy/codacy-cloud-cli/commit/f039b39922440cb29d2d7e0ea7c7ea5091c3eb42) Thanks [@alerizzo](https://github.com/alerizzo)! - Add a `--reanalyze-and-wait` (`-w`) variant to the `repository` and `pull-request` commands. Unlike `--reanalyze` (which triggers analysis and exits), this blocking variant captures a baseline of the current issues, triggers the reanalysis, polls until it finishes (every 10s, up to 20 minutes), and then prints how long the analysis took and what changed — issue deltas by pattern, severity, and category. Supports `--output json`.
+
 ## 1.1.1
 
 ### Patch Changes

.changeset/issues-overview-noise.md

@@ -1,6 +1,6 @@
 {
   "name": "@codacy/codacy-cloud-cli",
-  "version": "1.1.1",
+  "version": "1.2.0",
   "description": "A command-line tool to interact with Codacy Cloud from your terminal",
   "homepage": "https://www.codacy.com",
   "repository": {