bridgetown-image-pipeline 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4b506abefc78cfff32c2485ca39d6cd789486ffde30b52060e9aee52a2333510
-  data.tar.gz: 5bf51dd415078908778245b62003e4e36417519bb134e174e470bb77573f2f8c
+  metadata.gz: 2ad90fe01d5bc5d5ca76f72ae24e0cabca9af803516ca4b69570d5e6a95b601c
+  data.tar.gz: 16552338a9cf2653629ca8647f0e416c352c3446510306647d92b6ba5c4730c4
 SHA512:
-  metadata.gz: 8bd6e9145bf27b2ca0156ee67ce008bae9b3648d458baf7ec46adcbbddd34cc2e777c7436fee2a8882f8c90bb77954574e12149a937cd4d00290d5a7ab9001e3
-  data.tar.gz: 3d2cc00f6657d78ebf7c5777d6d28b8e1e46e116a500e991373c324d140c1c55f4b4ea9e28bfbace1d8d2f5b9c23249b4aa0e02e96633b4a2a1f1cbe08385f21
+  metadata.gz: 72d44062cfacc1ab027bd78b2f735fc4ce8f77240cc62c14b1aed8fefb9fe9d175fa476ab47553039858975fb2ce28805496401d1d5f84fd64eabc65d727456d
+  data.tar.gz: 6493826ccaa572137ca1e704ffbcdd78599f978f10f562d23f6670304d1663c9ee88edffa602a987e8cfec300d9da2e8373ea8e3d36c7040452db688eedb7971

data/CHANGELOG.md

@@ -6,6 +6,22 @@ project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [0.1.1] - 2026-05-19
+
+### Fixed
+
+- Processor no longer emits a duplicate fallback variant when the source
+  image's format already matches one of the configured `formats`. With
+  `formats: [:webp]` and a `.webp` source, each width was generating two
+  identical variants and the rendered `<picture>` `<source srcset>` had
+  double entries per width (#9).
+
+### Internal
+
+- Added `.bridgetown-cache/` to `.gitignore` so it stops showing up in
+  plugin-repo working trees when the plugin is exercised from a host
+  site checkout.
+
 ## [0.1.0] - 2026-05-15
 
 Initial release. Extracted from

data/RELEASING.md

@@ -0,0 +1,95 @@
+# Releasing
+
+How to cut a new release of `bridgetown-image-pipeline`. Two paths: **manual** (`rake release` from your machine) and **automated** (push a tag, GitHub Actions publishes via Trusted Publishing).
+
+## Pre-flight checks
+
+Run these before bumping the version:
+
+```sh
+bundle exec rake test       # all green
+bundle exec rake rubocop    # clean
+bundle exec rake build      # gem builds without warnings
+```
+
+Optional sanity: unpack the built gem and confirm no stray files shipped.
+
+```sh
+gem unpack pkg/bridgetown-image-pipeline-X.Y.Z.gem -t /tmp/unpacked
+ls /tmp/unpacked/bridgetown-image-pipeline-X.Y.Z
+```
+
+Make sure `.bridgetown-cache/`, fixtures, and test files are not included.
+
+## Version + changelog
+
+1. Bump the constant in [lib/bridgetown/image_pipeline/version.rb](lib/bridgetown/image_pipeline/version.rb).
+2. Add a dated section to [CHANGELOG.md](CHANGELOG.md) describing the changes since the last release.
+3. Commit both changes together:
+
+   ```sh
+   git commit -am "Release vX.Y.Z"
+   ```
+
+## Path A — manual release (current default)
+
+`bundler/gem_tasks` (loaded in [Rakefile](Rakefile)) provides `rake release`. It will:
+
+- Build the gem into `pkg/`
+- Create a `vX.Y.Z` git tag
+- Push the commit and tag to `origin`
+- Push the `.gem` to rubygems.org using credentials in `~/.gem/credentials`
+
+```sh
+bundle exec rake release
+```
+
+Requires `gem signin` to have been run once on this machine. Credentials live at `~/.gem/credentials` (chmod 600).
+
+## Path B — automated release via GitHub Actions
+
+[.github/workflows/release.yml](.github/workflows/release.yml) publishes on any `v*` tag push using rubygems.org Trusted Publishing (OIDC, no stored API key).
+
+**One-time setup** (already done? skip):
+
+1. **rubygems.org** → gem page → Trusted Publishers → add:
+   - Repository: `beflagrant/bridgetown-image-pipeline`
+   - Workflow filename: `release.yml`
+   - Environment: `rubygems`
+2. **GitHub** → repo Settings → Environments → create `rubygems`. Optionally restrict to tags matching `v*`.
+3. The gem must already exist on rubygems.org (Trusted Publishing won't create a new gem). First release must be a manual `rake release` or `gem push`.
+
+**Release flow once set up:**
+
+```sh
+# bump version.rb and CHANGELOG.md
+git commit -am "Release vX.Y.Z"
+git tag vX.Y.Z
+git push origin main --tags
+```
+
+The workflow runs tests, then `rubygems/release-gem@v1` builds and pushes. Watch the Actions tab.
+
+> `rubygems/release-gem@v1` expects the gemspec version to match the tag — drift fails loud. That's a feature.
+
+## After publishing
+
+- Confirm the version appears on https://rubygems.org/gems/bridgetown-image-pipeline.
+- Smoke test in a clean dir: `gem install bridgetown-image-pipeline -v X.Y.Z` then `ruby -rbridgetown/image_pipeline -e 'puts Bridgetown::ImagePipeline::VERSION'`.
+- Close any milestones / linked issues.
+
+## Yanking a broken release
+
+If a release is broken, yank within minutes of publishing rather than letting installs spread:
+
+```sh
+gem yank bridgetown-image-pipeline -v X.Y.Z
+```
+
+Yanked versions can't be re-pushed under the same number. Bump to `X.Y.Z+1` and release a fix. Note the yank in CHANGELOG.md.
+
+## Notes
+
+- `rake release` and the Action both rely on the gemspec's `files` glob — keep it tight so test fixtures and cache dirs stay out of the published gem.
+- Trusted Publishing supersedes the older `RUBYGEMS_API_KEY` secret pattern. Do not add that secret if it isn't already there.
+- Pre-release versions (`X.Y.Z.pre1`, `X.Y.Z.rc1`) work the same — tag them `vX.Y.Z.pre1` for the Action to fire.

data/lib/bridgetown/image_pipeline/processor.rb

@@ -17,6 +17,7 @@ module Bridgetown
         source_height = image.height
         original_ext  = File.extname(source_path).downcase.delete(".")
         original_ext  = "jpg" if original_ext == "jpeg"
+        original_fmt  = original_ext.to_sym
 
         variants = []
 
@@ -27,7 +28,14 @@ module Bridgetown
             variants << build_variant(source_path, basename, target_width, fmt)
           end
 
-          variants << build_variant(source_path, basename, target_width, original_ext.to_sym)
+          # Generate a fallback variant in the source's own format so the
+          # <img src> always has something to point at, but skip it when
+          # the configured formats already cover the source format —
+          # otherwise variants ends up with duplicates (e.g. webp source
+          # with formats=[:webp] would emit each width twice).
+          next if @config.formats.include?(original_fmt)
+
+          variants << build_variant(source_path, basename, target_width, original_fmt)
         end
 
         {

data/lib/bridgetown/image_pipeline/version.rb

@@ -2,6 +2,6 @@
 
 module Bridgetown
   module ImagePipeline
-    VERSION = "0.1.0"
+    VERSION = "0.1.1"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: bridgetown-image-pipeline
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Jim Remsik
@@ -86,6 +86,7 @@ files:
 - CHANGELOG.md
 - LICENSE.txt
 - README.md
+- RELEASING.md
 - Rakefile
 - docs/INTERNALS.md
 - docs/adr/0001-bg-image-delivery-via-image-set.md
@@ -127,7 +128,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.6
+rubygems_version: 3.6.9
 specification_version: 4
 summary: Build-time AVIF/WebP image derivatives and helpers for Bridgetown.
 test_files: []