v0.3.0 — settings by scope

What's Changed

• Put the how-to on the page the banner sends people to by @nitinhayaran in #14
• Split the console by what each thing actually belongs to by @nitinhayaran in #16
• Call this 0.3.0 by @nitinhayaran in #17

Full Changelog: v0.2.1...v0.3.0

Updating to this release

Your Edgemetry is its own repository — the deploy button imported this one
rather than forking it, so GitHub gives you no Sync fork button.

In your copy: Actions → Update Edgemetry → Run workflow, then merge the
pull request it opens. Merging is what deploys. Your data and your Cloudflare
configuration are untouched — they live in D1 and in Cloudflare, not in the
repository.

No such workflow? Your copy predates it, and needs one manual update to get
it. From a clone of your repository:

git remote add upstream https://github.com/hayaran/Edgemetry.git
git fetch upstream main
git reset --hard upstream/main
git reset --soft origin/main
git commit -m "Update Edgemetry"
git push

That takes upstream's files as one ordinary commit on your own history, which
is what makes it apply cleanly to a repository that shares no history with
this one. It replaces every tracked file, so read the diff first if you have
edited any.

Full detail in the README

v0.2.1

What's Changed

• Only hedge the count when the feed was actually truncated by @nitinhayaran in #12
• Call this 0.2.1 by @nitinhayaran in #13

Full Changelog: v0.2.0...v0.2.1

Updating to this release

Your Edgemetry is its own repository — the deploy button imported this one
rather than forking it, so GitHub gives you no Sync fork button.

In your copy: Actions → Update Edgemetry → Run workflow, then merge the
pull request it opens. Merging is what deploys. Your data and your Cloudflare
configuration are untouched — they live in D1 and in Cloudflare, not in the
repository.

No such workflow? Your copy predates it, and needs one manual update to get
it. From a clone of your repository:

git remote add upstream https://github.com/hayaran/Edgemetry.git
git fetch upstream main
git reset --hard upstream/main
git reset --soft origin/main
git commit -m "Update Edgemetry"
git push

That takes upstream's files as one ordinary commit on your own history, which
is what makes it apply cleanly to a repository that shares no history with
this one. It replaces every tracked file, so read the diff first if you have
edited any.

Full detail in the README

v0.2.0 — update checking

What's Changed

• Add a static demo built from the dashboard itself by @nitinhayaran in #1
• Harden the deployment story, and split it out of the README by @nitinhayaran in #2
• Add content security policy to demo HTML for enhanced security by @nitinhayaran in #3
• Move the tracker URL out of deploy config and into the dashboard by @nitinhayaran in #4
• Document the hostname step the deploy button leaves to you by @nitinhayaran in #5
• Bound the ingest body by bytes read, not by what it claims by @nitinhayaran in #7
• Collapse the post-deploy steps Getting started now covers by @nitinhayaran in #6
• Give the console a tab icon and the avatar a real menu by @nitinhayaran in #8
• Tell people when they are behind, and give them a button to catch up by @nitinhayaran in #9
• Say "10+" when ten is all the feed could tell us by @nitinhayaran in #10
• Call this 0.2.0 by @nitinhayaran in #11

New Contributors

• @nitinhayaran made their first contribution in #1

Full Changelog: https://github.com/hayaran/Edgemetry/commits/v0.2.0

Updating to this release

Your Edgemetry is its own repository — the deploy button imported this one
rather than forking it, so GitHub gives you no Sync fork button.

In your copy: Actions → Update Edgemetry → Run workflow, then merge the
pull request it opens. Merging is what deploys. Your data and your Cloudflare
configuration are untouched — they live in D1 and in Cloudflare, not in the
repository.

No such workflow? Your copy predates it, and needs one manual update to get
it. From a clone of your repository:

git remote add upstream https://github.com/hayaran/Edgemetry.git
git fetch upstream main
git reset --hard upstream/main
git reset --soft origin/main
git commit -m "Update Edgemetry"
git push

That takes upstream's files as one ordinary commit on your own history, which
is what makes it apply cleanly to a repository that shares no history with
this one. It replaces every tracked file, so read the diff first if you have
edited any.

Full detail in the README