Bill Commons

MN SF 4115

died on adjournment

A resolution condemning Hinduphobia and anti-Hindu and reaffirming Minnesota's commitment to religious freedom, inclusion, and mutual respect

Minnesota · 2025-2026 · upper

Quick answers

Did MN SF 4115 pass?

No. MN SF 4115 died when the 2025-2026 session adjourned without final action on it. Bills that die this way are sometimes reintroduced in a later session. Latest recorded action (2026-03-18): Author added Westlin

What is MN SF 4115 about?

MN SF 4115 is a bill in the 2025-2026 titled “A resolution condemning Hinduphobia and anti-Hindu and reaffirming Minnesota's commitment to religious freedom, inclusion, and mutual respect”.

Who sponsors MN SF 4115?

Limmer is the primary sponsor of MN SF 4115, joined by 4 cosponsors.

Introduced
2026-03-04
Latest action
2026-03-18 — Author added Westlin
Bill type
bill
Last updated
—

Subjects

Sponsors

  • Limmerprimary
  • Kreuncosponsor
  • Hoffmancosponsor
  • Latzcosponsor
  • Westlincosponsor

Committees

Not provided by source.

Action timeline

  1. 2026-03-04

    Introduction and first reading

    introduction

  2. 2026-03-04

    Referred to Judiciary and Public Safety

    referral-committee

  3. 2026-03-05

    Author added Latz

  4. 2026-03-18

    Comm report: To pass and re-referred to Rules and Administration

    committee-passage,referral-committee

  5. 2026-03-18

    Author added Westlin

Versions

Documents

Votes

Not provided by source.

Related bills

Official source

https://www.revisor.mn.gov/bills/94/2026/0/SF/4115?list=open&body=Senate

Attribution

Data from openstates_bulk_csv, retrieved 2026-07-24T05:24:48.331508Z

Inspect retained evidence for changes recorded after evidence tracking began:

Source and document changesStatus and relationship changes

Use this data

Every field on this page is available from the free public API — no key or licence required. Fetch this bill as JSON: GET /api/v1/bills?jurisdiction=MN&identifier=SF 4115. See the API docs or the MCP server for AI assistants.

Known limitations

  • Sponsor party and chamber affiliation are not yet captured by this API.
  • Committee referrals are not yet captured.

See the methodology page for data sources and limitations.