laminas / .github

Laminas Organization Templates

Laminas Organization Templates

🇷🇺 Русским гражданам

Мы, участники Laminas, родились и живем в разных странах. У многих из нас есть друзья, родственники и коллеги как в России, так и в Украине. Некоторые из нас родились в России. Некоторые из нас живут в России. У некоторых бабушки и дедушки сражались с фашистами во Второй мировой войне. Здесь никто не поддерживает фашизм.

У одного из нас есть украинская родственница, которая спаслась из дома вместе с сыном. Поезд задержался из-за бомбежки на дороге впереди. У нас есть друзья, которые прячутся в бомбоубежищах. Мы с тревогой ждем весточки от них после воздушных налетов, которые беспорядочно наносят удары и попадают по больницам, школам, детским садам и домам. Мы не берем это из каких-либо СМИ. Мы наблюдаем это напрямую.

Вы доверяете нам достаточно, чтоб использовать наши программы, и мы просим вас довериться нам вновь. Мы нуждаемся в помощи. Выходите и протестуйте против этой бесполезной войны. Остановите кровопролитие. Скажите "Нет войне!"

🇺🇸 To Citizens of Russia

We at Laminas come from all over the world. Many of us have friends, family and colleagues in both Russia and Ukraine. Some of us were born in Russia. Some of us currently live in Russia. Some have grandparents who fought Nazis in World War II. Nobody here supports fascism.

One team member has a Ukrainian relative who fled her home with her son. The train was delayed due to bombing on the road ahead. We have friends who are hiding in bomb shelters. We anxiously follow up on them after the air raids, which indiscriminately fire at hospitals, schools, kindergartens and houses. We're not taking this from any media. These are our actual experiences.

You trust us enough to use our software. We ask that you trust us to say the truth on this. We need your help. Go out and protest this unnecessary war. Stop the bloodshed. Say "stop the war!"

This repository contains templates used by all (or most) repositories in this organization.

In particular:

• Community Health Files:
  • Backwards Compatibility Break Template
  • Bug Template
  • Code of Conduct
  • Contributing Guidelines
  • Feature Request Template
  • Getting Support
  • Pull Request Template
  • Security Policy
• Travis Build Templates:
  • Supported PHP versions build template
• Shared Tool Configurations:
  • Renovate

.github's Issues

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

None detected

---

• Check this box to trigger a request for Renovate to run again on this repository

CONTRIBUTING.md has a broken link

Bug Report

Summary

The file CONTRIBUTING.md has a broken link here:

If you are working on new features or refactoring, create a proposal.

Expected behavior

Where is this supposed to go to?
If to create a RFC against a component, I am not sure how this can be done.
If against this repo, then link can be fixed to https://github.com/laminas/.github/issues/new?labels=RFC&template=RFC.md&title=%5BRFC%5D%3A+%5BTITLE+OF+RFC%5D

Let me know and I will submit a PR accordingly

Prevent renovate from ever merging PRs

Bug Report

In service manager repo renovate opened lockfile maintenance PR against default branch that was 3.21.x at the time. Since then default branch changed to 4.0.x and CI issues were fixed in that branch. On the next lockfile maintenance attempt renovate force pushed updates from the new default branch 4.0.x and since CI passed it auto-merged the PR that was still opened against old default branch 3.21.x.
See laminas/laminas-servicemanager#197 and the renovate PR in question laminas/laminas-servicemanager#185

This exposed flawed behavior that can have serious consequences while we are unaware.

As such auto-merging of pull requests must be entirely disabled in renovate config. That will not affect the lockfile maintenance flow of automerging branch without creating the PR.

Pull Request Template still contains refs to `MASTER` branch

https://raw.githubusercontent.com/laminas/.github/master/.github/PULL_REQUEST_TEMPLATE.md

• TARGET THE master BRANCH

`require-dev` upgrades don't seem to respect `composer.json` constraints

Bug Report

require-dev upgrades don't seem to respect composer.json's config.platform.php definition, nor the existing dependency ranges.

Probably caused by #39.

This affects following patches (big list):

• laminas/laminas-mail#215
• laminas/laminas-diagnostics#54
• mezzio/mezzio-authorization-rbac#22
• mezzio/mezzio#132
• mezzio/mezzio-session#42
• laminas/laminas-mvc-middleware#30
• mezzio/mezzio-hal#62
• mezzio/mezzio-hal#61 (note the two PRs around mezzio-hal)
• laminas/laminas-di#80
• laminas/laminas-cache-storage-adapter-test#40
• laminas/laminas-code#148
• mezzio/mezzio-session-cache#33
• mezzio/mezzio-session-ext#38
• laminas/laminas-dependency-plugin#51 (note: in this case, the error only appeared in CI, not in renovate)
• mezzio/mezzio-swoole#104
• laminas/laminas-session#62
• mezzio/mezzio-skeleton#92
• laminas/laminas-recaptcha#27
• laminas/laminas-view#182
• laminas/laminas-view#181 (note the two PRs around laminas-view)
• laminas/laminas-escaper#40
• mezzio/mezzio-skeleton#91 (note how mezzio-skeleton doesn't have a config.platform.php)
• mezzio/mezzio-skeleton#90 (second mezzio-skeleton patch)
• laminas/laminas-cache-storage-adapter-ext-mongodb#36
• laminas/laminas-servicemanager#161
• laminas/laminas-cache#234
• laminas/laminas-cache-storage-adapter-redis#54

Disable semantic commits

Feature Request

Q	A
New Feature	yes
RFC	no
BC Break	no

Summary

Semantic commits (prepending, type(scope): to commit messages) are useful for JS/TS projects that are using semantic-release, however as this is a PHP based framework, we can turn off the "auto" feature and disable it outright.

Note: I'm creating these and assigning them to myself as a reminder.