# Changelog of Website Tech Stack Monitor: Added & Removed (`mmdincer/website-tech-stack-monitor`) Actor

- **URL**: https://apify.com/mmdincer/website-tech-stack-monitor/changelog.md
- **Full Actor documentation**: https://apify.com/mmdincer/website-tech-stack-monitor.md

## Changelog

### 1.1.1

- When opening the named baseline store fails with HTTP 403 or `insufficient-permissions`, the run uses its default key-value store and continues. Apify's automated QA token cannot create named stores; that path used to crash before any website was checked. A first look still finishes as `baseline_saved`. Runs that can create `website-tech-stack-monitor-state` still keep the baseline there.

### 1.1.0

- Pay per event via `Actor.charge`: `site-checked` once per website whose page was read. `apify-actor-start` is the platform start event. Technology rows, failed reads and websites left unread because of the spending limit are not charged.
- A charge result of zero is not treated as the spending limit. That result means pay-per-event is not applied on the run. The websites are still delivered.
- Prices in `pricing-ppe.json` (about $0.003 to $0.006 per website; the file uses $0.005 on the free plan and $0.0005 to start) are set on the platform.

### 1.0.0

- First release. Reads one public page per website (HTML, response headers and script URLs) and names technologies from an original fingerprint catalogue.
- The first run saves a baseline and lists the stack. Later runs with the same watchlist name report technologies that were added or removed.
- Does not scrape BuiltWith or any other technology-lookup website. Obeys `robots.txt`. A bot-protection page stops the check and is not worked around.
- No pay-per-event price is configured.