Skip to content

Pre-Alpha Release(s) 14.0.2-14.0.4 > Beta - #1497

Open
briankalwat wants to merge 827 commits into
masterfrom
beta
Open

Pre-Alpha Release(s) 14.0.2-14.0.4 > Beta#1497
briankalwat wants to merge 827 commits into
masterfrom
beta

Conversation

@briankalwat

Copy link
Copy Markdown

Notice

In case you are submitting a non bug-fix-PR, we highly recommend you to engage in a PR discussion first.

There are many factors we consider before accepting a pull request. This includes:

  1. Whether or not the Rock system you run is a standard, main-line build. If it is not, there is a lower chance we will accept your request since it may impact some other part of the system you don't regularly use.
  2. Features that would be used by less than 80% of Rock organizations, or ones that don't match the goals of Rock.

With the PR discussion we can assess your proposed changes before you start working on it so that we can come up with the best possible approach to it. This may include:

  1. Coming up with an alternate approach that does not involve changes to core.
  2. Advising how your proposed solution be done in a different way that is more efficient and consistent with the rest of the system.
  3. Have one of our core developers make the changes for you. This may be the case if the change involves intricate tasks like an EF migration or something similar.

Proposed Changes

Fixes: #

Types of changes

What types of changes does your code introduce to Rock?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality, which has been approved by the core team)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • This is a single-commit PR. (If not, please squash your commit and re-submit it.)
  • I verified my PR does not include whitespace/formatting changes -- because if it does it will be closed without merging.
  • I have read the Contributing to Rock doc
  • By contributing code, I agree to license my contribution under the Rock Community License Agreement
  • Unit tests pass locally with my changes
  • I have added any required unit tests or integration tests that prove my fix is effective or that my feature works
  • I have included updated language for the Rock Documentation (if appropriate)

Further comments

Documentation

Migrations

If your pull request requires a migration, please exclude the migration from the Rock.Migration project, but submit it with your pull request. Please add a note to your pull request that provides a heads up that a migration file is present.

Panha-Sim and others added 30 commits May 18, 2026 16:26
… to consolidated DueSoonCounts and OverdueCounts merge field into the ConnectionRequestCounts merge field.
…values correctly when opened in auto-edit mode, which could result in those values being cleared when the group was saved.
… the HighlightDetailColumn, and updated the column so its per-column filter searches both the title and detail.
# Conflicts:
#	Rock.JavaScript.Obsidian/Framework/SystemGuids/serviceJob.ts
#	Rock.Version/AssemblySharedInfo.cs
… cause the grid to not properly update when scrolling vertically on small devices. (Fixes SparkDevNetwork#6839)
…values correctly when opened in auto-edit mode, which could result in those values being cleared when the group was saved.

(cherry picked from commit 1e9327c)
…ubmission List and Form Analytics to Obsidian, and added Confirmation Email Both, Notification Email multi-address, and Connection Requests automations.
kylehenning and others added 30 commits June 8, 2026 10:38
… header and deactivation confirmation, other fixes.
…non-US address verification and optional geocoding. Requires a Smarty subscription for 'International Address Verification' or, if using geocoding, 'International Geocoding'.
…eing logged when the viewer connected over IPv6. (Fixes SparkDevNetwork#6843)
…ion-related blocks, ensuring they open with a clean route instead of an unsightly query-string URL, by standardizing the communication blocks on the single, longstanding "CommunicationId" page parameter.
…ion-related blocks, ensuring they open with a clean route instead of an unsightly query-string URL, by standardizing the communication blocks on the single, longstanding "CommunicationId" page parameter.
# Conflicts:
#	Rock.Blocks/Communication/CommunicationList.cs
…ng included in Universal Search results after a bulk re-index, and restored the missing "Indexing Enabled" option in the Attributes block so Attributes can be flagged for indexing. (Fixes SparkDevNetwork#6857)
…s each request's prayer comments with a single efficient query. Ref: 2635df6
…ock by widening it to fit the maximum possible exception Id.
…f any remaining legacy Azure Blob Storage usage to the core Azure Blob Storage provider, including BinaryFile rows whose StorageEntitySettings still reference the legacy keys, and then deactivates the legacy provider.
…-day events like camps, retreats, and mission trips can be entered as days rather than total hours.
…on's (or spouse's) email address when the optional Email field was left blank on submission. (Fixes SparkDevNetwork#6861)
# Conflicts:
#	Rock/Attribute/Helper.cs
#	Rock/Model/Core/AttributeValue/AttributeValue.SaveHook.cs
Pre-Alpha Release(s) 20.0.2-4 > Beta Rock
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.