[PR #372] [MERGED] Lock linter version to fix new failures. #558

Closed
opened 2026-03-03 12:30:36 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/fsouza/fake-gcs-server/pull/372
Author: @mheffner
Created: 11/28/2020
Status: Merged
Merged: 11/30/2020
Merged by: @fsouza

Base: mainHead: chore/lock-lint-version


📝 Commits (2)

  • bd06fc3 Lock linter version to fix new failures.
  • b1251d3 Lock lint in GHA as well

📊 Changes

2 files changed (+3 additions, -1 deletions)

View changed files

📝 .github/workflows/main.yml (+2 -0)
📝 Dockerfile (+1 -1)

📄 Description

Lock the linter to version v1.32 to prevent failures on more recent linter versions. This gets the main branch building again and would isolate future lint cleanups.

Grabbed change from #370


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/fsouza/fake-gcs-server/pull/372 **Author:** [@mheffner](https://github.com/mheffner) **Created:** 11/28/2020 **Status:** ✅ Merged **Merged:** 11/30/2020 **Merged by:** [@fsouza](https://github.com/fsouza) **Base:** `main` ← **Head:** `chore/lock-lint-version` --- ### 📝 Commits (2) - [`bd06fc3`](https://github.com/fsouza/fake-gcs-server/commit/bd06fc34e7a4bc76daebb3a98385946f2437a8cb) Lock linter version to fix new failures. - [`b1251d3`](https://github.com/fsouza/fake-gcs-server/commit/b1251d39e75c8c49b02a340e6d8f637478a99129) Lock lint in GHA as well ### 📊 Changes **2 files changed** (+3 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/main.yml` (+2 -0) 📝 `Dockerfile` (+1 -1) </details> ### 📄 Description Lock the linter to version v1.32 to prevent failures on more recent linter versions. This gets the main branch building again and would isolate future lint cleanups. Grabbed change from #370 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-03 12:30:36 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/fake-gcs-server#558
No description provided.