Skip to content

Releases

LinkForge v1.2.4 — Fix What's New modal repeating

Choose a tag to compare

@sushantkumar-web sushantkumar-web released this 16 Sep 10:46

Hotfix

Fixed

  • The "What's New" modal was showing on every page reload. Root cause: the modal relied on a client-side POST to /release-notes/dismiss to mark the version as seen, but that POST was failing silently on some hosts, so the DB never recorded the dismissal.
  • Fixed by marking the version as seen the moment the modal is rendered on the server side. The dismiss button is now cosmetic — the outcome is recorded before the user can interact.

Guarantee: the modal now shows exactly once per release, regardless of browser, host, or POST failure.

No migrations. No database changes. Safe to apply over any v1.2.x.

LinkForge v1.2.3 — CSS Cache Fix

Choose a tag to compare

@sushantkumar-web sushantkumar-web released this 16 Sep 10:41

Hotfix

Fixed

  • tokens.css was loaded via @import inside app.css, so it had no version query string. Browsers and CDNs (Cloudflare) cached it for 6 months — design token changes never reached users after updates.
  • Fixed by concatenating tokens.css into app.min.css at build time. Single stylesheet, invalidated by the ?v= query string on the <link> tag.

No migrations. No database changes. Safe to apply over any v1.2.x release.

LinkForge v1.2.2 — Hotfix: Release Notes Fallback

Choose a tag to compare

@sushantkumar-web sushantkumar-web released this 16 Sep 10:18

Hotfix for v1.2.1

Fixed

  • The "What's New" modal wasn't appearing after updating to v1.2.1 because release notes were only written for v1.2.0. The lookup was exact-match only, so any hotfix version with no notes entry showed nothing.

Improved

  • ReleaseNotes::for() now falls back to the closest earlier version that has notes. So v1.2.2 (and any future hotfix) will surface the notes from v1.2.0 automatically. Release notes only need to be written for major / minor bumps — not for every patch.

Upgrade path

  • From v1.1.x or earlier → apply v1.2.2 directly.
  • From v1.2.0 → apply v1.2.2. Migrations are unchanged.
  • From v1.2.1 → apply v1.2.2. Only the ReleaseNotes class changed.

No migrations, no database changes. Safe to apply over any v1.2.x release.

LinkForge v1.2.1 — Fix UTM presets migration

Choose a tag to compare

@sushantkumar-web sushantkumar-web released this 16 Sep 10:02

Hotfix for v1.2.0

Fixed

  • Migration 009_utm_presets_v2.sql assumed the utm_presets table existed. On installs upgrading from v1.1.x, the table was never created, so the migration failed and aborted the entire chain — migrations 010 and 011 never ran either.
  • Fixed by making migration 009 create the table first via CREATE TABLE IF NOT EXISTS, then apply column additions conditionally. Fully idempotent.

Upgrade path

  • From v1.1.x or earlier → apply v1.2.1 directly. Migrations 009, 010, 011 will all run cleanly.
  • From v1.2.0 → apply v1.2.1. Migration 009 re-runs idempotently (no-op if table exists). 010 and 011 run for the first time.

LinkForge v1.2.0 — UTM Builder, Bot Filtering & What's New

Choose a tag to compare

@sushantkumar-web sushantkumar-web released this 16 Sep 08:25

What's new in v1.2.0

UTM Preset Builder
Reusable campaign tracking templates. Build a preset once with source / medium / campaign / term / content, then attach it to any link. LinkForge appends the UTM parameters to the destination URL automatically. Includes a live preview in the create-link modal. Manage presets at /utm-presets.

Bot Filtering
Google, Bing, Facebook link previews, Telegram, WhatsApp unfurls, uptime monitors, SEO tools, and headless clients no longer count as clicks. Bots are still redirected correctly — they just don't appear in analytics. This fixes the classic "I shared a link but nobody clicked yet and it says 2 hits" problem. Toggle in Settings → Security.

What's New Modal
After each update, users see a clean modal explaining what changed — right on the dashboard. Shows once per version. No more "read the changelog" links.

Help Sidebar
New Help section in the sidebar linking to Documentation, Bug Reports, and Contact. URLs hardcoded to the official LinkForge channels.

Under the hood

  • New BotDetector core class with 80+ patterns (search engines, social unfurlers, monitors, headless browsers, scanners, dev tools)
  • New ReleaseNotes core class for version-aware release notes
  • Bundle builder now appends all JS files correctly (fixed in v1.1.2)

Migrations (auto-applied on update)

  • 009_utm_presets_v2.sql — adds user_id, utm_term, utm_content to utm_presets
  • 010_bot_filtering.sql — seeds bot filtering setting (enabled by default)
  • 011_release_notes.sql — seeds release notes tracking setting

No breaking changes. Safe to apply over v1.1.2.

LinkForge v1.1.2 — Fix JS bundle

Choose a tag to compare

@sushantkumar-web sushantkumar-web released this 16 Sep 07:23

Critical hotfix

What was broken in v1.1.1
The bundle builder in build.sh had a bug where each iteration truncated the output file instead of appending. The result: only the last file (links.js) made it into app.bundle.js. utils.js, app.js, and search.js were silently dropped, which broke:

  • Copy button (missing copyToClipboard)
  • Mobile sidebar toggle (missing toggleSidebar)
  • Modal open/close helpers
  • Search dropdown

Fixed in v1.1.2

  • Bundle builder now writes the banner once and appends every file
  • Added a JS_COUNT safety check — build aborts if zero files are bundled
  • Prints each bundled file for visibility

No migrations, no database changes. Safe to apply over v1.1.1.

LinkForge v1.1.1 — Production fix for broken JS

Choose a tag to compare

@sushantkumar-web sushantkumar-web released this 16 Sep 07:04

Hotfix for v1.1.0 production issue

Fixed

  • HTML minifier was corrupting inline JavaScript in <script> blocks, causing all buttons on /links (Edit, Copy, Create link) to fail silently on production
  • Removed unsafe regex-based JS minification from build.sh — was breaking code at build time
  • Added storage/backups/ folder to the release archive so it exists on fresh installs

Improved

  • JavaScript is now bundled into a single app.bundle.js file (one HTTP request instead of three)
  • <script> and <style> blocks are now protected from the HTML minifier
  • Bundle and CSS files include a version banner comment

No migrations, no database changes. Safe to apply over v1.1.0.

LinkForge v1.1.0 — Custom Domains, Targeting, Responsive Design & Captcha

Choose a tag to compare

@sushantkumar-web sushantkumar-web released this 16 Sep 06:32

What's new in v1.1.0

Custom Domains
Serve short links from your own domain like go.company.com. DNS verification via TXT record. Primary-domain selector. Redirect engine routes custom-domain requests transparently.

Geo/Device Targeting
Route visitors to different destinations based on device (mobile/desktop/tablet) or country. Configured per-link via a collapsible editor inside the create and edit modals. Country detection works automatically behind Cloudflare.

Responsive Design
Mobile sidebar drawer with hamburger menu and backdrop. Tables scroll horizontally. Modals adapt to viewport height. KPI cards stack. Bulk action bar adapts to narrow viewports.

Premium Color Refresh
Rewrote design tokens with a deeper 5-tier surface hierarchy, refined indigo accent (#6E7BF2), brighter status colors, proper button press-down states, hover glow, and subtle nav-active accent bars.

Captcha Protection (optional)
Support for Cloudflare Turnstile, Google reCAPTCHA v3, and hCaptcha. Opt-in via Settings → Security. Fails open if the provider is unreachable. Driver-based — one setting switches providers.

Webhooks
Real-time event delivery with HMAC-SHA256 signature, retry queue with exponential backoff, and full delivery log. Events: link.created, link.updated, link.deleted, link.clicked.

Link Detail Page
Unified view at /link?id=X with Overview / Analytics / QR / Activity / Edit tabs.

Also in this release

  • Global analytics dashboard with time-range switcher
  • Search with / keyboard shortcut
  • Tags, bulk actions, users management
  • Password reset flow with SMTP
  • System Health page (migrations, cache, filesystem, features)
  • Dashboard / and Links /links are now separate pages
  • DB backup before migrations
  • Duplicate slug UX with suggestion pills
  • Favicon set

Migrations (auto-applied on update)

  • 004_webhooks.sql
  • 005_api_logs_index.sql
  • 006_custom_domains.sql
  • 007_link_targeting.sql
  • 008_captcha_settings.sql

Tested on
PHP 8.2 / 8.4 · MySQL 5.7+ / MariaDB 10.4+ · Chrome, Safari, Firefox (desktop + mobile viewports)

LinkForge v1.0.4 — Installer and migration system fix

Choose a tag to compare

@sushantkumar-web sushantkumar-web released this 15 Sep 13:41

Critical fix — installer and updater

This release fixes a broken installer and updater in v1.0.3 that prevented fresh installs and updates from working correctly.

What was broken in v1.0.3:

  • InstallController had malformed SQL (duplicate columns, missing commas) that failed to create a fresh database
  • Missing migration files for password_resets, auth_tokens, api_request_logs, utm_presets, and email settings
  • Update system used a db_version counter instead of per-file tracking, so new migrations were never run on existing installs

What's fixed in v1.0.4:

  • New MigrationRunner class with filename-based tracking via the schema_migrations table
  • All migrations are idempotent — safe to re-run
  • Fresh install path fully tested end-to-end
  • Update path shares the same runner as install
  • Config file is rolled back if install fails partway through

If you installed v1.0.3: please reinstall using v1.0.4. The v1.0.3 installer may have left your database in a partial state.

LinkForge v1.0.3 — Developer Platform Update

Choose a tag to compare

@sushantkumar-web sushantkumar-web released this 15 Sep 13:12

⚠️ This release has a broken installer. Do not use for fresh installs or updates. Please use v1.0.4 instead.

Changes in v1.0.3

Core

  • Smart Expiration Fallback: expired links now redirect to a secondary URL instead of a bare 410 page
  • Real, scannable QR codes via phpqrcode (previous implementation was decorative only)
  • Fixed global HTML minifier corrupting PNG and CSV responses

Developer Platform

  • API key engine with SHA-256 hashed storage, per-key scopes (links:read / links:write), per-key rate limits, and live telemetry
  • Full REST API v1: create, list, update, delete, analytics
  • Comprehensive API documentation page
  • Role-based API rate cap (user: 120, admin: 500, super_admin: 1000 req/min)

Productivity

  • Live topbar search with / keyboard shortcut and full-page results
  • Tags page with click totals, click-to-filter from any link row
  • Bulk actions: select many links, disable / enable / delete in one action
  • Global Analytics dashboard: KPI cards, time-range switcher, top links, traffic sources, devices, browsers, OS breakdown
  • Duplicate slug UX with clickable suggestion pills

Auth & Email

  • Password reset flow with token-based email links
  • Driver-based Mailer: log (dev), smtp (production), mail (legacy)
  • Settings → Email UI with SMTP configuration and one-click test email
  • Role-based access control: super_admin, admin, user
  • Users management page

Under the hood

  • Reserved slug protection (blocks login, api, links etc from user claim)
  • Cache auto-creation with OPcache invalidation
  • Sanity-checked build script that refuses to package secrets