# denoland/fresh · RepoSense Release & Migration Intelligence

> fix: change post_publish upload target to S3 by @crowlKats. Drop-in upgrade. Migration: None.

## Metadata
- **Repository URL**: https://github.com/denoland/fresh
- **Primary Package**: `$fresh` (NPM)
- **Categories**: `FRAMEWORK`, `RUNTIME`
- **Latest Version**: `v2.3.3`
- **Semantic Status**: `COMPATIBLE`
- **Bundle Size Impact (unavailable)**: `Size Unavailable`
- **Atom Ingestion Feed**: https://github.com/denoland/fresh/releases.atom

## The Human Context (Plain-English Pitch)
$fresh is an open-source library and developer tool in the denoland/fresh ecosystem. It saves developers from writing repetitive low-level boilerplate from scratch by providing a battle-tested, open-source implementation ready for production.

## Stage 1 Executive Summary ([Core Change] + [Required Action] + [Migration Effort])
fix: change post_publish upload target to S3 by @crowlKats. Drop-in upgrade. Migration: None.

## Breaking Changes & Required Actions
- fix: change post_publish upload target to S3 by @crowlKats in #3745
- revert: bring back Babel CJS transform by @bartlomieju in #3798

## Migration Snippet
```ts
npm install $fresh@2.3.3
```

## Ecosystem Compatibility Matrix & Graph Warnings
- **TypeScript 5.x** [`COMPATIBLE`]: Ships standard TypeScript declaration files without type regressions.

## Zero-Noise Release Timeline
- **v2.3.3** (2026-04-28) [COMPATIBLE]: fix: change post_publish upload target to S3 by @crowlKats. Drop-in upgrade. Migration: None.

## Upgrade & Migration Q&A (GEO Direct Answers)
### Is denoland/fresh v2.3.3 safe to upgrade in production?
denoland/fresh v2.3.3 is classified as COMPATIBLE (PATCH release). fix: change post_publish upload target to S3 by @crowlKats. Drop-in upgrade. Migration: None.

### What breaking changes or compatibility risks exist in denoland/fresh v2.3.3?
No breaking API changes or peer dependency conflicts are recorded for denoland/fresh v2.3.3 in the RepoSense compatibility graph.

### What is the bundle size impact of $fresh v2.3.3?
Measured bundle size telemetry is currently unavailable for $fresh v2.3.3; verify build output locally before deploying.

### How do I upgrade $fresh to v2.3.3?
Upgrade $fresh to v2.3.3 by running "npm install $fresh@2.3.3" and applying the migration steps: npm install $fresh@2.3.3