The earlier deadline matters for candidates preparing declarations, nominating petitions or certificates of nomination, and for voters tracking which contests may take shape before the November 3, 2026, general election.

What must be filed by August 18

Under Oregon’s 2026 elections calendar, August 18 is the last day for an elected incumbent district candidate seeking reelection to the same office to file a declaration of candidacy or nominating petition.

The same date applies to a local elected incumbent candidate filing for an office filled at the general election. It also is the deadline for a nonaffiliated or minor political party elected incumbent candidate to file a certificate of nomination.

Those filing types are not interchangeable. Declarations of candidacy and nominating petitions apply to the local and district candidacies identified in the state calendar. Certificates of nomination apply to nonaffiliated and minor-party candidates.

Most other candidates have until August 25

August 18 is not the deadline for every local candidate. The later deadline is August 25, 2026, for local candidates other than elected incumbents seeking reelection to the same office.

August 25 also is the deadline for district candidates who are not elected incumbents seeking the same office, and for nonaffiliated or minor-party candidates who do not fall into the covered incumbent category.

Oregon’s calendar lists August 25 as the August election day and separately lists that date as the filing deadline for the candidates outside the August 18 incumbent categories. The election-day entry and the candidate-filing entry are separate parts of the calendar.

Where candidates file

The filing office depends on the office sought:

• County offices: File with the county elections official.
• City offices: File with the city elections official.
• District offices: File with the county elections official in the county where the district’s administrative office is located.

Oregon’s Secretary of State says local charters and ordinances may supersede the general guidance. Candidates should confirm the correct forms, filing hours and submission requirements with the applicable filing officer before filing.

Portland provides a verified example of the two-step schedule. The city says filing for City Auditor and City Council positions closes for incumbents at 5 p.m. August 18 and for non-incumbents at 5 p.m. August 25.

Fees, signatures and campaign finance

Submitting paperwork does not by itself guarantee that a candidate will appear on the ballot. Candidates may be required to pay a filing fee or submit signatures in lieu of a fee, and the filing officer may need to review the submission for compliance.

Campaign-finance obligations are separate from the candidacy filing. The Oregon Secretary of State says candidates generally must file campaign-finance information with the Elections Division regardless of where they file their candidacy, with exceptions including federal candidates and precinct committee persons.

Voters’ pamphlet procedures are also separate. County, city and metropolitan service district candidates should ask the applicable county elections office whether a pamphlet will be published and how statements may be submitted.

What voters should watch next

Candidate lists may continue to change after the filing deadlines. The Oregon Secretary of State provides a candidate-filings search and a list of open offices for the 2026 general election.

The scheduled withdrawal deadline for candidates other than district candidates is August 28, 2026. That date does not mean every candidate field will be fully settled or that all filings will have completed review by then.

Voters can check the state candidate-filings system and their county or city elections office to see which candidates have filed, which offices are open and whether local procedures affect a contest. The general election is scheduled for November 3.

For candidates covered by the earlier deadline, the immediate date is August 18. The practical next step is to confirm the filing officer, forms, fees or signature requirements, campaign-finance obligations and any local charter rules before submitting paperwork.

Sources

• Oregon Secretary of State: Run for Public Office
• Portland Elections

The construction launch took place in early July 2026. Eugene Mayor Kaarin Knudson and state officials participated in the launch, according to reporting on the project.

A separate Gate A6 upgrade

The City of Eugene also announced a separate $1 million state investment for infrastructure improvements at Gate A6. The funding comes through House Bill 5204.

The Gate A6 work will replace and relocate a passenger boarding bridge that is about 50 years old. The project is intended to expand hold-room space and improve gate operations, reliability and energy performance.

Hold rooms are the areas where passengers wait before boarding. Relocating the bridge is expected to support the revised gate layout while addressing aging equipment.

City-owned airport

Eugene Airport is owned and operated by the City of Eugene. The Concourse A project represents a major public-facing investment in the airport, which serves as part of the region’s transportation network.

The expansion is the larger of the two projects now associated with the airport’s construction activity. The Gate A6 improvements focus on a specific boarding area, while the Concourse A work is intended to address broader overcrowding and passenger-facility needs.

Construction is now underway. Public announcements about the launch did not establish a final completion date for the full Concourse A expansion or specify how many additional gates or passengers the completed project will accommodate.

Verrus submitted its first city-review application on July 31, 2026, starting a formal review of the proposed data center. The project has been publicly described as the Oakline at Mill Creek data center.

Council discusses possible moratorium

The Salem City Council held a public meeting August 3 to discuss whether the city should impose a moratorium on new data centers. The city manager’s office has identified data-center review as an active issue for the council and the community.

A city public calendar listed another council meeting for August 10. The calendar establishes the next scheduled council meeting but does not establish that the council will adopt a moratorium or take final action on the project.

The proposal has drawn strong public opposition at a Salem council meeting, according to a report by Tom’s Hardware. That report also identified the project as a $5.1 billion proposal by Verrus.

Technical questions remain in review

City staff have held introductory, development-process and technical meetings with Verrus and the Salem Economic Development Corporation, or SEDCOR. The technical discussions covered site design, transportation access, utility needs, environmental considerations and possible preservation of heritage oak trees.

The review could shape decisions involving Salem’s power, water, transportation, land use and tax base. A moratorium could also determine whether similar large data-center proposals move forward under the city’s current rules.

The project remains a proposal undergoing city review. The city has not disclosed final electricity demand, water consumption, tax revenue, construction employment or the project’s development-application status beyond the initial submission.

The district posted a construction update on July 22, 2026, identifying the closure as an operational change for the school year. The affected building is on the Redmond High School campus in Redmond, Oregon.

What is changing

The announcement concerns the school’s main academic building. It does not state that the entire Redmond High School campus will close, but the building will be unavailable during the 2026-27 school year while construction activity continues.

Students, staff and families should therefore expect a changed campus layout and construction-related disruption during the school year. The building closure is the specific operational effect identified in the district’s update.

The timing places construction work directly within regular school-year operations. Rather than affecting only an off-season period, the project will shape how the Redmond High School campus is used throughout the 2026-27 school year.

Bond work reaches campus operations

The construction is part of the district’s 2025 capital bond program, which voters approved. That approval established the funding and project context; the July 22 update now identifies a specific consequence for Redmond High School students and employees.

The development marks a move from bond authorization to work that affects daily use of a school facility. Redmond School District 2J’s announcement connects the building closure to construction rather than describing it as a permanent school closure or a change to the district’s academic program.

The update identifies the 2026-27 school year as the affected period. It does not set out a separate construction completion date or announce changes to school start times, transportation or extracurricular schedules.

For Redmond families, the confirmed change is that the main academic building will not be available during the 2026-27 school year. The district’s construction update provides the school-year timeframe and ties the work to the voter-approved 2025 bond program.

The new charges will add at least $13 per month for utility customers, creating an immediate recurring cost as the city works to address the multimillion-dollar operating gap.

The fees apply to Beaverton utility bills. The change affects customers beginning with bills issued in August, according to reporting by Beaverton Beat.

What the council approved

The council approved two new monthly fees. Together, they are expected to generate revenue for the city’s General Fund, which is facing a $16.2 million deficit.

The publicly reported minimum increase is $13 per month. That figure should not be read as an exact increase for every household or account. The individual names and amounts of both fees have not been identified in the available public description of the decision.

The charges are also separate from the broader question of how the city will close its operating gap. The stated purpose of the fees is to help address the deficit, but the reported action does not establish that the new charges alone will resolve the full $16.2 million shortfall.

Why the change matters

Utility bills are recurring household expenses, so the decision creates a direct monthly cost for Beaverton customers rather than a one-time payment. At the reported minimum, a $13 monthly increase would amount to $156 over a full year for an account billed at that level.

Actual annual costs will depend on the charges applied to an individual utility account. The city’s public website provides city-government notices, meetings and public-service information, while the reported fee details identify the August start date, the minimum monthly increase and the budget problem the council is seeking to address.

The action also places the city’s financial challenge on utility bills. The General Fund deficit is an operating-budget issue, while the new fees are collected through utility billing. For residents, that means the fiscal response will be visible in a bill they receive each month.

What happens next

The first practical milestone is the August 2026 billing cycle, when customers are expected to see the new fees. Beaverton residents should review their bills for the new line items and compare the total with prior monthly charges.

The City Council’s approval establishes the fees, but the reported information does not identify a separate end date or describe the charges as temporary. It also does not provide a full fee schedule showing how the two fees are divided among customer accounts.

For now, the confirmed change is that Beaverton utility customers will face at least $13 more in monthly charges beginning in August, while the city uses the new revenue as part of its response to a $16.2 million General Fund deficit.

The decision follows public debate over Oakline at Mill Creek, a proposed data center in southeast Salem that has been described as a potential $5.1 billion development. Verrus is the developer identified with the project.

The moratorium immediately changes the regulatory path for future data-center proposals in Salem. It also places the city’s review of data-center rules at the center of the next phase of debate over Oakline at Mill Creek.

What the council action does

The pause applies for one year to new data-center development, according to reporting on the council action. During that period, Salem is considering zoning and infrastructure rules for data centers.

That work could address how data centers fit within the city’s land-use framework and how related infrastructure requirements are handled. The available public descriptions of the action do not establish that the moratorium cancels or rejects the Oakline at Mill Creek proposal.

Verrus had submitted a city review application before the moratorium was considered, according to reporting. That timing makes the status of the application an important part of the project’s path, but the moratorium itself should not be treated as a final approval or denial of the proposed facility.

Why Oakline is central to the debate

Oakline at Mill Creek is the project that brought the data-center question into sharper public view. The proposed facility is in southeast Salem, and its reported potential value of $5.1 billion has made it a major development proposal for the city.

That figure describes the project’s potential reported value, not committed investment. The project’s size and configuration remain tied to the city review and developer filings rather than a completed development.

The council’s action came after a July 27 public meeting that drew attention to the proposal and the broader question of data-center development in Salem. The public debate included opposition to the potential AI data center, according to Tom’s Hardware.

For residents, businesses and property owners, the pause means Salem will examine the rules before allowing new data-center development to move ahead under the current framework. The practical effect is a temporary stop on new development proposals while the city works through its policy questions.

What happens next

Salem’s next step is to consider zoning and infrastructure standards for data centers during the one-year moratorium. The city’s public meeting calendar records the council meetings surrounding the action and the subsequent discussion.

The council’s decision does not, by itself, resolve the future of Oakline at Mill Creek. The project’s review status, including how the submitted application is treated during the moratorium, will determine how the proposal proceeds as Salem develops its rules.

For now, the clearest change is the citywide pause: Salem has chosen to take one year to examine the rules for data centers before new development can move forward.

The action places the fire among the major incidents receiving Oregon’s statewide wildfire-response support. The Oregon State Fire Marshal described the 2026 invocation as the 11th statewide use of the emergency authority.

Evacuation readiness around Mount Hood

Wasco County had Level 1, Level 2 and Level 3 evacuation orders connected to the incident when the state fire marshal issued its July 29 release. Those levels represent escalating readiness and movement instructions for people in affected areas.

The release did not establish a current evacuation level specifically for Welches. Welches is an unincorporated community in the Mount Hood corridor of Clackamas County, where wildfire smoke, evacuation readiness and travel conditions can affect residents, visitors and local businesses.

For people using the Mount Hood corridor, the fire’s effects can include changing smoke exposure and potential disruptions on Highway 26. The incident also matters to tourism and to emergency agencies working to protect homes and critical infrastructure. Fire acreage and evacuation conditions can change after an incident update, so residents and travelers should rely on current emergency notices when making decisions.

Federal assistance and local preparation

Oregon also secured a Fire Management Assistance Grant for the Grasshopper Fire. The federal assistance can cover up to 75% of eligible firefighting costs, helping support the response while state and local agencies work on fire suppression and community protection.

Clackamas County’s emergency planning has included a separate Mount Hood Great Escape exercise. The county reported that the two-day exercise tested responses to a major wildfire and a Public Safety Power Shutoff scenario.

The exercise addressed countywide emergency preparedness and focused on the kinds of conditions that can complicate wildfire response: evacuation coordination, loss of power and protection of communities in the Mount Hood area.

The known response step for the Grasshopper Fire is ongoing state and local firefighting coordination under the emergency conflagration action, supported by the federal grant. The July 29 state release provided the mapped acreage and evacuation information for that date; it did not establish a later containment figure or a new deadline for the response.

The appearance did not resolve the dispute. Portland continues to pursue a land-use violation notice tied to the alleged breaches, while the legal question of whether the facility violated its approved use remains active.

What Portland alleges

The city says federal records document 25 alleged violations during a 10-month period beginning in October 2025. The allegations concern detainees who Portland says were held overnight or beyond the amount of time allowed under the property’s land-use approval.

That condition is central to the case. Portland’s position is that the facility’s approval permits certain detention-related activity only within defined time limits. The city alleges those limits were exceeded repeatedly, rather than claiming that every aspect of the facility’s operation violated local rules.

Portland has issued or pursued a land-use violation notice related to the alleged breaches. The notice represents the city’s effort to use its permitting and land-use authority in a dispute involving a facility used by ICE and a landlord responsible for the property.

Why the case matters

The case puts a local land-use condition against the operation of a federal immigration facility. Its outcome could help determine how Portland enforces conditions attached to properties used for federal operations or federal contracts.

For city officials, the issue is whether the approved use of the property includes a meaningful limit on how long people may be held there. For the facility and its landlord, the dispute concerns whether the alleged detention practices fall outside the use authorized for the site.

The case also illustrates the difference between a city enforcement allegation and a court finding. Portland’s count of 25 alleged violations is based on the city’s interpretation of federal records. The allegations have not been established as final adjudicated findings against ICE or the landlord.

A court ruling could clarify whether the land-use condition applies as Portland contends and what enforcement options are available if the court agrees with the city. The dispute may therefore affect more than the specific notice: It could define the practical reach of Portland’s local permitting authority at a federally used site.

The dispute remains open

The July 10 appearance was an update in ongoing litigation, not a final decision. The city and the facility’s landlord remain in the court dispute over the property’s approved land use.

No final ruling or completed enforcement remedy followed the hearing. The next stage will determine how the court addresses Portland’s allegations and whether the city’s land-use notice can lead to an enforceable result.

Until that process is complete, the 25 alleged violations remain claims in an unresolved case. The central question is whether overnight or extended holds breached the detention-time limits attached to the facility’s land-use approval.

The action followed public concern about data-center expansion and its impacts, according to reporting on the city’s decision. It changes the path for new proposals, while two applications that reportedly entered the permitting process before the pause are expected to be handled under the rules in effect before the vote.

Pending applications are treated differently

The distinction between existing applications and future proposals is central to the decision. The two data-center applications that preceded the pause are expected to continue through the permitting process under the earlier land-use rules.

That does not mean either project has received final approval. The applications remain proposals moving through the city’s development system, while projects submitted after the pause face the temporary restriction.

The two applications have been described as having reached permitting before the city acted. The applicants and proposed capacities have not been identified in the public information surrounding the decision.

For Hillsboro residents, property owners and businesses, the immediate consequence is a change in how new data-center proposals can move forward. Projects already in the process are separated from later applications based on when they entered permitting.

Growth and infrastructure are at the center of the debate

Hillsboro’s decision raises a broader land-use question: whether existing development rules are adequate for a major growth industry whose facilities can require substantial sites and supporting infrastructure.

Public concern was part of the discussion leading to the pause. The action itself does not establish a specific environmental, utility or transportation impact from either pending application. Those proposals should therefore not be treated as having been found to cause a particular impact.

Instead, the temporary measure gives city officials time to consider how future data-center development should be evaluated. The result could affect the rules applied to new proposals, although the pause is not a permanent ban and does not itself resolve the city’s longer-term policy.

The Hillsboro Herald reported on a special city meeting concerning a data-center moratorium resolution. The city’s public announcements provide information about Hillsboro development and planning activity.

Airport land-use appeals have an August hearing

A separate Hillsboro land-use matter is scheduled for Aug. 18, 2026, when a combined de novo public hearing will address two appeals involving Hillsboro Airport land use.

The airport proceeding is separate from the data-center pause. It is part of the city’s broader 2026 land-use and planning calendar, which also includes major development and anniversary projects.

The next steps on data centers will determine how the temporary pause is applied to future proposals and how the two earlier applications proceed under the previous rules. The airport appeals, meanwhile, have a specific next date: the combined public hearing scheduled for Aug. 18.

The hearing is scheduled to begin at 6 p.m. The commission will consider whether to recommend the proposed amendments to the council. The matter has not yet been approved, and the Planning Commission had not issued a recommendation as of Aug. 10.

What the hearing could change

The Town Center Building Height Waiver concerns how the city handles requests for buildings that may exceed standard height limits in the area. The proposed amendments could influence how tall future Town Center buildings may be, although the city’s public notice does not identify a proposed maximum height or provide the full text of the changes.

The hearing is part of a broader city review of Town Center zoning provisions. Wilsonville previously established a limited-duration task force to examine provisions related to building-height waivers. The Planning Commission’s role on Aug. 12 is to hear the proposal and decide whether to recommend it to the next decision-making body, rather than take final action on the city’s development rules.

Next step at City Council

The city says a Wilsonville City Council hearing is scheduled for Sept. 10. That hearing is the next identified step if the proposal proceeds from the Planning Commission. The council’s consideration could determine whether the proposed code amendments move forward.

The height-waiver discussion comes as the city separately considers how to support development and address blighted areas in Town Center. On July 21, Wilsonville reported results from a statistically valid resident phone survey conducted in June. A plurality of voters who responded said they were aware of and supportive of using tax-increment financing to address blighted areas in Town Center.

The city’s related materials also reference 121 Vuela homes serving households at 30% to 80% of area median income. That housing information and the survey findings provide broader context for the city’s Town Center discussions, but support for tax-increment financing does not establish support for every proposed building-height change.

Residents seeking to weigh in on the waiver proposal can attend the Planning Commission’s Aug. 12 public hearing. The commission’s recommendation, followed by the council’s scheduled Sept. 10 hearing, will determine the next public step for the amendments.

The fire was reported at 46,071 acres and 0% contained in an Oregon State Fire Marshal update. Firefighters focused structure-protection efforts along the Snake River corridor from Huntington to Brownlee Reservoir.

Highway closed across eastern Oregon

The Oregon State Fire Marshal said major closures were in effect between Baker City and Huntington after the fire reached I-84 overnight. The closure disrupted a major regional route used by local travelers, freight operators and emergency responders.

The Associated Press reported a broader closure of approximately 70 miles of I-84 between Baker City and Ontario. AP later reported that the route reopened on July 27, although the full duration of the closure and all resulting detour effects were not specified.

The highway closure affected travel planning for people moving through Baker County and communities along the eastern Oregon corridor. It also underscored the need for residents and visitors to monitor changing fire and road conditions during the response.

State task force focuses on protecting structures

Oregon mobilized a task force through its Immediate Response program to help defend homes and critical infrastructure. The deployment added state resources as firefighters worked near Huntington and along the Snake River.

AP reported that firefighters were building dozer lines around Huntington near a railroad to protect critical infrastructure. The reported protection priorities extended toward Brownlee Reservoir, where crews were working to limit the fire’s threat to structures and other essential facilities.

The July 27 update described the fire as 0% contained. It did not provide a later containment figure or a final fire status. The available incident details also do not establish that Baker City was evacuated or that the fire entered city limits.

For Baker City residents, the immediate effects were the I-84 closure and the need to account for rapidly changing conditions near the city and along the Snake River corridor. The known next step was continued structure protection and fire response while state and local authorities managed access and safety around the fire.

SE High School Drive is closed from June 11 through Aug. 17, 2026, between SE Spy Glass Ridge Drive and SE 48th Place. During the same period, SE 48th Place is restricted to local and emergency vehicles between SE Jetty Avenue and SE 51st Street.

The restrictions affect how residents, workers, emergency responders and other travelers reach properties and destinations near the two named street segments. The SE 48th Place restriction does not apply to local and emergency vehicles, according to the city’s project notice.

Replacement work continues into 2026

The city says the project began in summer 2025 and is continuing during the 2026 construction season. Its stated purpose is to replace aging water and sewer infrastructure in the Nelscott area. The planned work covers about 1,900 feet of lines.

Replacing the older lines is intended to improve the area’s water and sewer infrastructure and support longer-term system reliability. The project is part of broader public-works and infrastructure activity underway in Lincoln City during 2026.

For people who normally use SE High School Drive or the affected portion of SE 48th Place, the posted street limits provide the current access schedule. The closure and restriction are tied to the stated construction period, rather than a citywide traffic change.

Aug. 17 is the posted closure end date

The city identifies Aug. 17, 2026, as the end date for the SE High School Drive closure. That date does not establish that the entire Nelscott project will be finished at the same time; the project information describes construction as continuing through summer 2026.

The City of Lincoln City also cautions that project schedules and budgets may change. Residents and businesses near the work can use the named street segments and dates to plan access during the summer construction season, while emergency and local access remains available on the restricted section of SE 48th Place.

The results reported by Lincoln County showed each councilor leading the vote to remain in office. The election involved six separate recall contests, with ballots mailed to 1,821 eligible Waldport voters.

How each recall vote stood

Greg Dunn led the vote against recall, 363 to 299. Rick Booth led, 401 to 265, while Susan Woodruff led, 400 to 269.

Jayme Morris led the vote to remain in office, 363 to 270, according to the Lincoln County News report. Michelle Severson led, 406 to 259, and Jerry Townsend led, 384 to 278.

In each contest, the lower total represented votes supporting the recall and the higher total represented votes to retain the councilor.

The Lincoln County News reported 37% voter turnout in the count it described. A corroborating report said approximately 95% of ballots had been counted in the first release, with ballots arriving through the statutory deadline still subject to processing the following week.

Recall followed 2025 mayoral removal

The recall campaign followed the council’s April 2025 decision to remove the elected mayor from office, according to local reporting. The vote on the six councilors therefore tested whether the council’s membership would change after that dispute.

The first results did not change the council’s six elected members. They also did not resolve the underlying dispute over the mayor’s removal.

Three seats already headed to November ballot

Regardless of the recall outcome, three of the council seats were already scheduled to appear on the November 2026 general-election ballot because their terms expire at the end of the year. Those seats are held by Woodruff, Booth and Severson.

The mayor’s office was also scheduled for the November election because that term expires at year-end. The recall results thus leave the existing council in place for now, while the city moves toward a regularly scheduled election that will include three council seats and the mayor’s office.

The July 13 figures were first or unofficial results rather than a final certified canvass. Lincoln County’s election document listed scheduled unofficial-results releases, and additional ballots could still alter the totals.

The state’s wildfire response posture escalated again Aug. 6, when the Oregon State Fire Marshal mobilized resources to the Town Gulch Fire after Oregon invoked its Emergency Conflagration Act.

The two developments show Oregon using both federal assistance and state emergency powers during a year that officials warned could bring severe wildfire conditions. The grants provide financial support for wildfire response, while the state mobilization makes additional firefighting resources available for the Town Gulch incident.

Federal grants approved in July

Gov. Tina Kotek’s office announced that three Fire Management Assistance Grants had been approved during July 2026. The grants are intended to support wildfire response and can help reduce the financial burden of firefighting as Oregon agencies deploy crews and equipment.

The approvals are significant because major wildfire responses can require resources beyond what local agencies can manage on their own. Federal assistance gives the state and affected communities another source of support while suppression operations are underway.

The state announcement did not identify the dollar value of the three grants. Approval of the grants also does not mean they cover all firefighting costs.

State mobilizes for Town Gulch Fire

On Aug. 6, the Oregon State Fire Marshal said it had mobilized resources to the Town Gulch Fire. The action followed the invocation of Oregon’s Emergency Conflagration Act, a state authority used to coordinate a broader emergency response to a wildfire.

The mobilization places the Town Gulch Fire within Oregon’s statewide emergency-response framework. State agencies coordinate wildfire suppression, emergency management, air quality and public safety, making the response relevant beyond the immediate fire area.

The fire marshal’s public update did not state the fire’s acreage, containment percentage, number of structures threatened or evacuation count. Those details are important measures of an incident’s scale, but the available announcement focused on the state’s decision to mobilize resources.

Warnings preceded the actions

State wildfire leaders briefed Kotek in May about preparations for the 2026 fire season. The governor’s office cited severe drought and record-setting low snowpack as factors contributing to the wildfire risk.

At that time, nine Oregon counties were already under emergency declarations. The warnings provided an early indication that fire conditions could put pressure on local and state response systems well before the Town Gulch mobilization in August.

Drought and low snowpack can increase concern about wildfire conditions across the state, but they do not establish the size or severity of any individual fire. The Town Gulch response is therefore best understood as an incident-specific state action occurring within a broader season of elevated risk.

What the actions mean for Oregon

For Oregon communities, federal grant approval and state mobilization can help agencies obtain or sustain the personnel, equipment and emergency coordination needed during active wildfire operations. The assistance also reflects the financial demands placed on governments when fire suppression extends beyond routine local capacity.

The response involves the Oregon State Fire Marshal, the Oregon Department of Forestry and the Oregon Department of Emergency Management, along with the governor’s office and other public-safety partners. Their work spans suppression, emergency coordination, public safety and air-quality concerns.

The next known step is continued response to the Town Gulch Fire under the state’s emergency framework. Public announcements identified the Aug. 6 mobilization but did not set out a separate deadline for the response or provide a final outcome for the fire.

The vacancy figures were published July 23 in a release titled “Oregon Private Job Vacancies Unchanged in Second Quarter 2026.” The unemployment figure was reported separately by the department on July 15.

Together, the two measures show an Oregon labor market that remained broadly steady during the period covered by the latest state reports. Vacancies did not materially increase or decrease, and the June unemployment rate stayed at 5.2%.

What the figures show

The vacancy measure covers private job openings across Oregon in the second quarter of 2026. The department described those vacancies as unchanged from the prior period.

The unemployment rate is a separate statewide measure. At 5.2% in June, it indicates the share of Oregon’s labor force that was unemployed during that month. The department released that figure eight days before its report on private vacancies.

Because the measures track different parts of the labor market, neither one alone provides a complete picture. Job vacancies describe employers’ open positions, while the unemployment rate describes the portion of the labor force without a job. Read together, the latest reports indicate that Oregon had not experienced a material shift in either measure during the period reported.

The reports provide statewide Oregon figures. They do not, by themselves, identify whether vacancies were concentrated in particular regions, occupations or industries.

Why the numbers matter

For people looking for work, a flat vacancy count means the number of available private-sector openings was not reported as expanding in the second quarter. For employers, the same result indicates that the statewide supply of reported private openings did not materially change during the period.

The 5.2% unemployment rate adds another measure of the conditions facing Oregon workers. With vacancies holding steady rather than moving sharply higher or lower, the latest figures do not point to a major statewide change in the balance between available jobs and unemployed workers.

That matters for workforce-development planning because programs serving job seekers and employers rely on labor-market conditions to assess where demand is changing. The reported figures offer a broad statewide baseline, but they do not establish which occupations or communities may be experiencing stronger or weaker conditions.

The data also do not establish a cause for the vacancy trend. The Employment Department’s reports identify the reported vacancy and unemployment measures, but the figures alone do not show that a particular state policy or other single factor produced the result.

What comes next

The latest releases give Oregon residents two recent reference points: private job vacancies were unchanged in the second quarter, and unemployment was 5.2% in June. Future updates will show whether that stability continues or whether vacancies and unemployment begin to move in different directions.

For now, the central message from the state’s labor-market reports is one of limited change. Oregon’s private employers reported no material second-quarter shift in vacancies, while the statewide unemployment rate remained at 5.2% in the most recent monthly figure reported by the department.

The announcement places a major economic-development proposal under executive review and raises questions about how state property was offered, how the project was evaluated and when the public learned about it. It also means the proposed sale should not yet be treated as permanently canceled: Kotek announced an intention to reverse the transaction, but a formal legal instrument ending the sale has not been posted in the governor’s newsroom index.

Why the land sale drew attention

The proposed project involves 32 acres owned by the State of Oregon in Salem. The development was described as a roughly $5 billion data center, making the land transaction significant well beyond the acreage itself.

Public concern focused on transparency. Reports circulating about the proposal said residents and the governor learned of it only after the deal had been substantially developed. That concern has put the state’s process for disposing of public land and overseeing large development proposals at the center of the dispute.

The available public description does not establish that the data center was approved, fully financed or environmentally cleared. It describes a proposal that had advanced far enough to prompt a planned state land sale and public reaction.

What Kotek’s announcement changes

Kotek’s statement signals that the executive branch does not intend to allow the sale to proceed in its current form. The land remains a public asset unless and until the transaction is formally completed or terminated under the applicable legal terms.

For residents and taxpayers, the immediate questions are practical: whether the state will retain the property, whether any agreement or commitments must be unwound, and how the project was evaluated before the governor’s announcement. The public information currently identifies neither the terms of a sale cancellation nor any financing, utility or other development commitments connected to the proposal.

The matter also tests executive oversight. A project of the stated size could involve decisions about state property, economic development and public accountability. Kotek’s move indicates that those decisions are now being reconsidered at the governor’s level rather than treated as a routine land transaction.

Public meeting planned for Aug. 3

A public meeting about the proposed data center is scheduled for Aug. 3, 2026, at Salem Public Library. The meeting gives residents a forum to discuss the proposal and the state’s handling of the land sale after the governor’s announcement.

The timing matters because the next documented step is not a completed cancellation but public discussion and further clarification. The meeting may bring attention to how the proposal advanced, what state officials knew and what obligations, if any, remain associated with the sale.

Until Oregon issues a formal cancellation document or other definitive action, the status is best described as an intended cancellation of the state land sale. The proposed data center’s final development status, financing and infrastructure commitments remain unsettled in the public account.

The City of Eugene lists the restructuring among its current civic developments. For Eugene residents, the change could affect how fire protection and emergency medical services are governed, budgeted and coordinated. The available announcement does not establish that the split has been completed.

Key transition details are not yet available

The official material supplied for this report does not state a final separation date or an implementation schedule. It also does not provide a detailed staffing plan, explain how stations would be allocated, or identify a final financial and governance agreement between Eugene and Springfield.

The announcement likewise does not say how emergency-response zones or service levels would change. Those details will be needed to show how the restructuring would work in practice for residents and emergency personnel. The next known step is the transition planning associated with creating the two independent departments, but the supplied city information does not give a timetable for that work or for the final separation.

The project, called Oakline at Mill Creek, is proposed for the Mill Creek Corporate Center. The City of Salem describes it as a potential data-center operation, not an approved or guaranteed project.

The Salem City Council considered the one-year moratorium at a public meeting on Aug. 3, 2026. Later reporting described the city as announcing a pause that would halt new data-center development while officials review zoning rules for such facilities.

The available record does not include the final ordinance number, the council’s final roll-call vote or the full operative text of the moratorium. Those details are important for determining exactly which projects and applications are covered.

A major proposal still in an early stage

Salem’s July 14 project information page said Oakline at Mill Creek remained in an early stage. The city said formal planning, development, building, utility and other regulatory review would come later if Verrus determined that Salem was a viable location.

The city also said data centers are an allowed use in Employment Center zoning, subject to formal development review. That means the pause could affect how Salem evaluates future data-center proposals, but the available information does not establish that it automatically cancels or blocks Verrus’s project.

The city reported holding introductory, development-process and technical meetings with Verrus. Those discussions covered site design, transportation access, anticipated utilities, environmental considerations and preservation of heritage oaks.

The proposed site is within the 828-acre Mill Creek Urban Renewal Area, which the city says was prepared for industrial development. The project’s reported $5.1 billion value is a stated project scale, not a confirmed investment or completed construction cost.

Why the pause matters

The decision puts zoning and infrastructure questions ahead of the project’s next formal steps. Salem’s process would examine issues including access, utilities, environmental considerations and site design through the city’s development and permitting systems.

The city has not confirmed final electricity, water or wastewater demand figures for the proposed facility. Those impacts are to be evaluated through the formal application process rather than treated as settled facts at this stage.

The record also reflects heightened public attention. Tom’s Hardware reported that the council discussed the proposal at a July 27 public meeting. The report also said a company representative left a council meeting after a confrontation with protesters and was escorted out by police. The available sources do not establish additional details about the confrontation or identify any resulting legal action.

What happens next

The next clear steps depend on both the moratorium’s final terms and Verrus’s application status. The city’s July information page said no formal application had yet been received. Later reporting described an initial city-review filing, but the exact application type and current status were not established in the available record.

If a formal land-use application proceeds, the city says it would provide public notice and a 14-day public-comment period. After a land-use decision, the city’s stated process includes a 15-day appeal period.

For now, Salem is weighing new rules while a large proposed project remains in the pre-approval process. The moratorium’s final text, the city’s official vote record and the project’s permit file will determine how the pause applies in practice.

Instead of deciding whether to return an incumbent mayor to office, voters in The Dalles will choose among candidates seeking to become the city’s next mayor. The development concerns the City of The Dalles specifically, rather than another community in the Columbia Gorge.

What the report says

Columbia Community Connection described the contest as a three-way race to succeed Mays. That description provides an early view of the field, but it is not the same as a final or certified candidate list.

The available report does not identify all of the candidates or establish whether their filings are complete, formally accepted or otherwise confirmed through election records. As a result, the reported count of three candidates should be treated as qualified information until the county’s records verify the field.

The source material also does not state why Mays decided not to seek reelection. No reason for his decision is included beyond the report that he will not pursue another term after his third term.

What changes for voters

Mays’s decision removes the incumbent from the reported succession contest and puts the city’s next mayoral leadership at the center of the 2026 local election outlook. The change is relevant to The Dalles voters and to residents following the city’s municipal leadership, although the available source does not provide candidate platforms, campaign positions or reactions from local groups.

It also leaves important election details unresolved. The exact election date and filing deadlines were not established in the approved source material. Those details matter for determining when the contest will take place and who has officially qualified to appear before voters.

Next step

The next reporting step is to verify candidate filings and election deadlines through Wasco County election records. That review should establish which candidates have officially entered the race, whether the three-candidate description remains accurate and what dates apply to the contest.

For now, the confirmed development is Mays’s decision not to seek reelection after his third term. The July 24 report marks the opening of a new mayoral contest in The Dalles, while the formal candidate lineup and election calendar remain to be confirmed.

The budget keeps all 31 Portland fire stations open and preserves the city’s 157 parks, 11 community centers and 11 swimming pools. All Portland police officers and investigators also remain on the job.

Those protections do not mean city services are unchanged. The adopted plan discontinues approximately 140 positions from the city payroll and cuts affect shelters, parks and police support staff. The full operational effect of those reductions will depend on how city departments implement the budget.

What the budget preserves

The spending plan covers the fiscal year running from July 1, 2026, through June 30, 2027. Its most visible commitments are the continued operation of every fire station and the preservation of major parks and recreation facilities.

Keeping all 31 fire stations open preserves the city’s current station network. The budget also maintains funding for 157 parks, 11 community centers and 11 swimming pools, according to the City of Portland.

Police officer and investigator positions are preserved as well. That provision is separate from staffing reductions affecting police support positions, so the budget does not leave every police-related job or service unchanged.

Where reductions will be felt

The city’s approximately 140 discontinued positions are part of the response to the general-fund gap. The cuts also reach programs and staffing beyond the positions listed in the headline total, including shelters, parks and police support staff.

The source material does not provide a complete department-by-department accounting of the final reductions in the adopted budget. It also notes that sources differ slightly in how they describe the number and status of eliminated positions. For that reason, the approximately 140 figure is best understood as the overall adopted-plan estimate rather than a detailed count of every implementation change.

For residents, the practical question is how those staffing and program decisions translate into service levels during the fiscal year. The approved material says that implementation decisions will determine the full effect of reductions involving shelters and parks.

How the council reached the plan

The budget process began with a general-fund shortfall exceeding $160 million, according to the city’s May 20 account of the council’s earlier action. The final figure described with the adopted budget was approximately $170 million.

During the process, council amendments restored or preserved selected fire, public-safety and workforce programs. Those amendments helped maintain the fire-station network and other selected services even as the city moved forward with position and program reductions.

The council’s June 17 vote made the fiscal 2026-27 budget final. The city then faced the work of putting the adopted plan into effect across departments and programs.

Implementation remains a point of dispute

Implementation did not end the disagreement over the cuts. OPB reported on July 22 that the council later acted to save 30 jobs that had been slated for August layoffs, describing continuing disputes over how the adopted budget was being carried out.

That later action does not change the June 17 adoption date or the overall budget figures reported by the city. It does show that the final impact on individual positions can continue to change as departments and the council work through the plan.

For Portland residents, the budget sets the city’s spending and service framework through June 30, 2027: core public facilities and selected public-safety positions remain protected, while staffing reductions and cuts to shelters, parks and police support services move into implementation.

For residents and visitors using the recreation site, the change adds a direct parking cost and a new compliance step to trips that involve the site’s parking area. The requirement is already in effect, and the official park profile says a one-day permit can be purchased on site.

What changes for visitors

Gleneden Beach State Recreation Site remains open for day use year-round. The permit requirement does not change the site’s listed operating schedule. People arriving by vehicle should plan to obtain the required one-day permit when they park.

The official profile does not display the current dollar price of the permit in the reviewed text. Because the approved information does not provide a fee amount, no specific price is included here. The practical requirement is clear: drivers using the recreation-site parking area need the applicable one-day permit.

The site includes a parking area and a picnic area, along with a paved trail leading from the parking area to the beach. Those amenities remain part of the site’s official description. The available information characterizes the policy change as a parking-permit requirement, not as a closure.

Policy background and timing

Oregon State Parks’ FAQ identifies the March 30 change as the end of the parking-fee waiver at Gleneden Beach and other listed sites. The effective date is the key deadline for visitors: the requirement began March 30, 2026, rather than starting after a later transition period identified in the approved material.

Gleneden Beach is an unincorporated community in Lincoln County, Oregon. State Parks identifies the recreation site as being near Lincoln City, making the permit requirement relevant both to people in the local community and to visitors using the coastal facility.

The approved source packet does not provide current citation totals, enforcement figures, usage data or a separate later deadline. It does confirm the next practical step for visitors: purchase the one-day permit on site before using the parking area. The site’s year-round day-use status continues as of the current August 2026 reporting period.

For residents, property owners and local businesses, the hearing was the next formal opportunity to comment on a land-use decision in La Grande. The available record, however, does not identify the proposal’s title, applicant, parcel, requested action, acreage or zoning classification.

What the record shows

The City of La Grande Planning Commission packet dated July 14 states that the first City Council public hearing was scheduled for Aug. 5. It identifies the matter as part of the city’s formal planning process.

The packet extract does not establish whether the proposal involved a specific development project, a change to development standards or another planning action. It also does not provide a public-hearing result, amendment, approval or denial.

Because Aug. 5 had passed as of Aug. 8, the council’s final hearing record or minutes would be needed to determine what occurred. The materials supplied for this report do not include that later record.

Separate city and hospital developments

The city separately sought proposals in 2026 for a comprehensive Economic Development Strategic Plan. That effort is a separate development from the planning hearing and should not be treated as the subject of the council matter.

Grande Ronde Hospital Foundation also announced an $8.5 million fundraising campaign in summer 2026. The foundation identified expansion of the Regional Medical Center on Fourth Street as one of the projects on the horizon.

That hospital expansion is likewise separate from the planning hearing. The available planning record does not connect the council matter to the medical center project, and it does not provide enough information to describe the proposal’s possible effect on development, property or services in La Grande.

For now, the confirmed development is the scheduled City Council hearing in the city’s planning process. Any account of the proposal’s substance or final status would require the Aug. 5 council record or another official document identifying the action.