[PR #96] [MERGED] Pinned all dependencies #665

New issue

Closed

opened 2026-03-03 14:40:13 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 14:40:13 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/lipis/flag-icons/pull/96
Author: @lipis
Created: 9/25/2015
Status: ✅ Merged
Merged: 9/25/2015
Merged by: @lipis

Base: master ← Head: greenkeeper-pin

📝 Commits (1)

4d3eb8e chore(package): pinned dependencies

📊 Changes

1 file changed (+5 additions, -5 deletions)

View changed files

📝 package.json (+5 -5)

📄 Description

👋 Hello!

We’re all trying to keep our software up to date, yet stable at the same time.

This is the first in a series of automatic PRs to help you achieve this goal. It pins all of the dependencies in your package.json, so you have complete control over the exact state of your software.

From now on you’ll receive PRs whenever one of your dependencies updates – in real time. This way you get all the benefits of up-to-date dependencies, while having them pinned at the same time. This means:

No more surprises because some of your dependencies didn’t follow SemVer. Your software is always in a state you know about, regardless of when someone does $ npm install.
If you have continuous integration set up for this repo, it’ll run automatically. Ideally, it will pass and you'll stay up to date with the press of a button. If the updated dependency does break your software, it won’t affect your users, because their dependencies are still pinned to the working state.
You can immediately identify which dependency updates break your software, because each one is tested in isolation. You’ll also have a branch ready to work on, so adapting to new APIs is way faster.

Merge this PR and you’ll have up-to-date software without the headaches ✨

This pull request was created by greenkeeper.io.
It keeps your software, up to date, all the time.

_{Tired of seeing this sponsor message? Upgrade to the supporter plan!
You'll also get your pull requests faster ⚡}

_{🔄 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/lipis/flag-icons/pull/96 **Author:** [@lipis](https://github.com/lipis) **Created:** 9/25/2015 **Status:** ✅ Merged **Merged:** 9/25/2015 **Merged by:** [@lipis](https://github.com/lipis) **Base:** `master` ← **Head:** `greenkeeper-pin` --- ### 📝 Commits (1) - [`4d3eb8e`](https://github.com/lipis/flag-icons/commit/4d3eb8e9404cf4482e0ecbebe303c8d80c152a7b) chore(package): pinned dependencies ### 📊 Changes **1 file changed** (+5 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `package.json` (+5 -5) </details> ### 📄 Description :wave: Hello! We’re all trying to keep our software up to date, yet stable at the same time. This is the first in a series of automatic PRs to help you achieve this goal. It pins all of the dependencies in your `package.json`, so you have complete control over the exact state of your software. From now on you’ll receive PRs whenever one of your dependencies updates – in real time. This way you get all the benefits of up-to-date dependencies, while having them pinned at the same time. This means: - No more surprises because some of your dependencies didn’t follow [SemVer](http://semver.org/). Your software is always in a state you know about, regardless of _when_ someone does `$ npm install`. - If you have continuous integration set up for this repo, it’ll run automatically. Ideally, it will pass and you'll stay up to date with the press of a button. If the updated dependency _does_ break your software, it won’t affect your users, because their dependencies are still pinned to the working state. - You can immediately identify which dependency updates break your software, because each one is tested in isolation. You’ll also have a branch ready to work on, so adapting to new APIs is way faster. Merge this PR and you’ll have up-to-date software without the headaches :sparkles: --- This pull request was created by [greenkeeper.io](http://greenkeeper.io/). It keeps your software, up to date, all the time. <sub> Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster :zap: </sub> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>