# Changelog of Base64 Transcode — strict, both alphabets, per-item errors (`telyvar/text-base64-transcode`) Actor

- **URL**: https://apify.com/telyvar/text-base64-transcode/changelog.md
- **Full Actor documentation**: https://apify.com/telyvar/text-base64-transcode.md

## @telyvar/text-base64

### 0.1.2

#### Patch Changes

- Corrects a sentence in 0.1.1 that was wrong on the store page. It said the channel had been serving a description three weeks out of date. It had not: the output schema and the pre-filled example were already in the build of 2026-09-07, and the repository is what was behind — those files were uploaded fourteen hours before they were committed. The claim came from comparing git history against a build date, which cannot answer that question, and the runbook that prescribed it has been corrected too.

  Nothing about what the run does has changed in this release either. It exists because a published changelog said something false about this capability, and a correction belongs in the same place the claim was made.

### 0.1.1

#### Patch Changes

- A run now declares where its results and its report live, so a caller can see the shape of the answer before paying for one: one row per item in the order given, each carrying its index, and a report that counts what was delivered, what failed and what was never reached. The console also arrives pre-filled with a working example, including two strings that are deliberately invalid, so the failure rows can be seen without constructing them.

  Nothing about what the run does has changed. The transcoding is byte-identical to the version published on 2026-09-07. This release also adds a link from the store page back to telyvar.com, which did not exist when the previous build was made.