Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pull] dev from opf:dev #393

Merged
merged 30 commits into from
Feb 3, 2025
Merged

[pull] dev from opf:dev #393

merged 30 commits into from
Feb 3, 2025

Conversation

pull[bot]
Copy link

@pull pull bot commented Feb 3, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.1)

Can you help keep this open source service alive? 💖 Please sponsor : )

dombesz and others added 30 commits January 30, 2025 15:50
Bumps [factory_bot](https://github.com/thoughtbot/factory_bot) from 6.5.0 to 6.5.1.
- [Release notes](https://github.com/thoughtbot/factory_bot/releases)
- [Changelog](https://github.com/thoughtbot/factory_bot/blob/main/NEWS.md)
- [Commits](thoughtbot/factory_bot@v6.5.0...v6.5.1)

---
updated-dependencies:
- dependency-name: factory_bot
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [rubocop](https://github.com/rubocop/rubocop) from 1.71.0 to 1.71.1.
- [Release notes](https://github.com/rubocop/rubocop/releases)
- [Changelog](https://github.com/rubocop/rubocop/blob/master/CHANGELOG.md)
- [Commits](rubocop/rubocop@v1.71.0...v1.71.1)

---
updated-dependencies:
- dependency-name: rubocop
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Better structure upcoming meetings by organising them into named date sections
We addressed a bug with handling error responses during
OAuth 2.0 interaction with the identity provider.
Update omniauth-open_id_connect gem
…-entries-for-others

Do not allow time tracking for users that are not visible to you
…-6.5.1

Bump factory_bot from 6.5.0 to 6.5.1
When using accessing the instance using the wrong host name (different
from `Setting.host_name` configured in the administration or through env
vars), the app should still work.

The activities tab component is using a url to know where the activities
should be fetched from. This will trigger a CORS error when using the
wrong host name, and the activities will not be updated. By using a
relative path, the request will be relative to the current host, and
thus work correctly even when using the wrong host name.

I detected that during local development while using port 4200 instead
of 3000 as we usually do.
…ser-cf-filter-values-on-the-project-list

[#60972] Autocompleters for user cf filter values on the project list
…r-response-on-certain-attachment-constellation

fix unexpected passing of US-ASCII string into Commonmarker on search
Include ongoing in upcoming scope of schedule meeting
…-url-for-activities-refresh

Use relative path instead of url for activities refresh
@pull pull bot added the ⤵️ pull label Feb 3, 2025
@pull pull bot merged commit 99db98b into kp-forks:dev Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants