Bumped package json to 1.2.0

[mike182uk]

no ref

Bumped package json to 1.2.0 in preperation for tagged 1.2.0 release

[coderabbitai]

Walkthrough

The pull request updates the version field in package.json from 1.0.1 to 1.2.0. No other fields or configuration values are modified, and no code files are changed. This is a single-line version number update.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating the package.json version to 1.2.0.
Description check	✅ Passed	The description clearly relates to the changeset, explaining the version bump and its purpose for an upcoming release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bump-package-json

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@package.json`:
- Line 3: Update the repo to regenerate and commit an updated yarn.lock to
reflect the package.json version bump: after confirming the intended minor bump
from "version": "1.2.0" in package.json, run the package manager (yarn install)
to regenerate yarn.lock, add/commit the new yarn.lock, and push the change; also
update the PR description to note what changes justify the jump from 1.0.1 to
1.2.0 so reviewers can verify the version increase.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1fc61f62-bd39-4730-82a8-f4b59bc16048

📥 Commits

Reviewing files that changed from the base of the PR and between 402d791 and 70426e3.

📒 Files selected for processing (1)

• package.json

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash

echo "=== Checking for CHANGELOG ==="
fd -t f -i 'changelog' -E node_modules

echo -e "\n=== Checking for lock file ==="
ls -la yarn.lock package-lock.json 2>/dev/null || echo "No lock files found"

echo -e "\n=== Checking for other version references ==="
rg -n "1\.0\.1" --type-add 'config:*.{json,yml,yaml,toml,md}' -t config -g '!package.json' -g '!node_modules/**'

echo -e "\n=== Checking git tags to verify current version ==="
git tag -l "v1.*" | sort -V | tail -5

echo -e "\n=== Checking commits since v1.0.1 tag (if it exists) ==="
git log --oneline v1.0.1..HEAD 2>/dev/null | head -20 || echo "Tag v1.0.1 not found"

Repository: TryGhost/ActivityPub

Length of output: 365

---

Ensure yarn.lock is regenerated after version bump.

The version bump from 1.0.1 to 1.2.0 skips the 1.1.x range, which is unusual. While no CHANGELOG file exists in the repository, yarn.lock should be regenerated to reflect the version change in package.json.

The version jump's appropriateness cannot be verified without seeing the actual code changes since 1.0.1. Consider adding a note in the PR description documenting what new features or changes justify the minor version bump.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` at line 3, Update the repo to regenerate and commit an updated
yarn.lock to reflect the package.json version bump: after confirming the
intended minor bump from "version": "1.2.0" in package.json, run the package
manager (yarn install) to regenerate yarn.lock, add/commit the new yarn.lock,
and push the change; also update the PR description to note what changes justify
the jump from 1.0.1 to 1.2.0 so reviewers can verify the version increase.